Skip to main content
Glama

Builderlog

내 예전 글과 겹침 점검

blog_dup_check
Read-only

새 초안과 사용자가 붙여 넣은 예전 글 본문(최대 20편)을 글자 3개 묶음 코사인으로 견줘 많이 겹치는 글을 알려요. 뜻만 같고 낱말이 다른 글은 못 잡아요. 네이버 블로그를 직접 읽지 않고, 붙여 넣은 글을 저장하지 않아요.

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": {
      "body": "<body>",
      "past_posts": "<past_posts>"
    },
    "name": "blog_dup_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes새 초안 전체(200자 이상)
past_postsYes예전 글 본문들(각 200자 이상, 첫 줄 “# 제목” 이면 제목을 같이 보여 줘요)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnlyHint and closed-world annotations, the description discloses the matching algorithm, the false-negative behavior on paraphrases, and two data-handling facts: it does not fetch Naver Blog on its own and does not store pasted bodies. That is meaningful privacy and behavior context an agent would otherwise have to guess. It remains thin on how overlapping posts are ranked or returned.

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?

Three compact sentences: purpose plus method first, then the key limitation, then data-handling caveats. Nothing redundant, and the most decision-relevant information is front-loaded.

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 no output schema, the description covers what it does, what it cannot do, and what data it touches, which is enough to call it correctly. The one gap is that it only says it will 'tell you the overlapping posts' without any sense of the result shape or ranking, which matters somewhat given there is no output schema.

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%, so both parameters are already documented in the schema, and the description's details (20-post cap, trigram comparison on the pasted text) largely restate what maxItems and the field descriptions already say. Baseline 3 is correct when the schema carries the parameter semantics.

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

Purpose4/5

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

The description names a specific operation (comparing a new draft against pasted past posts), the resource involved, the scale (up to 20 posts), and even the comparison method (character-trigram cosine). An agent can immediately tell this is a similarity/duplication check rather than a general quality check. It stops short of naming which sibling to use instead, so it is not a 5.

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?

It clearly frames the input precondition (the user must paste past posts) and an explicit limitation — paraphrased content with different wording will not be caught — which tells an agent when this tool is the wrong fit. There is no explicit pointer to an alternative tool, so it lacks the when-not/alternative pairing that a 5 requires.

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