Skip to main content
Glama

Builderlog

댓글 분류와 답글 틀

blog_reply_triage
Read-only

사용자가 붙여 넣은 댓글(최대 20개)을 질문·감사·불만·광고 의심·개인정보 요청으로 나누고 종류별 답글 틀을 돌려줘요. 댓글을 읽어 오거나 달지 않고, 이메일·전화번호 모양은 가려서 보여 주며 저장하지 않아요.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "comments": "<comments>"
    },
    "name": "blog_reply_triage"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNo답글 말투 한 줄(선택, 예: 다정한 존댓말)
commentsYes댓글 본문들(최대 20개, 각 300자까지)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint/openWorldHint annotations, the description discloses privacy behavior that is not in any structured field: email and phone-number-like patterns are masked in the output and nothing is stored. It omits failure behavior (e.g. what happens above 20 comments), so it falls short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the core capability front-loaded and the privacy/scope constraints following. Every clause carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only tool with full schema coverage and no output schema, the description says enough: inputs come from pasted text, categories are enumerated, and the return is per-type reply templates. A slightly clearer sketch of the response shape would make it complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents both the `comments` array (max 20, 300 chars each) and the `tone` string with an example. The description restates the 20-comment limit but adds nothing about `tone` or item length, so the schema carries the parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (분류/나누고) and resource (댓글), then enumerates the exact output categories (질문·감사·불만·광고 의심·개인정보 요청) and adds that per-type reply templates are returned. This also separates it from its blog_* siblings, which check or draft content rather than triage pasted comments.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The statement '사용자가 붙여 넣은 댓글' and '댓글을 읽어 오거나 달지 않고' clearly imply when to use the tool (comments already pasted, no fetching or posting) and rule it out for retrieval/side effects. It still gives no explicit route to an alternative, though no sibling does the same job.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources