Skip to main content
Glama

Builderlog

내부 링크 후보 맞추기

blog_internal_links
Read-only

새 초안과 사용자가 붙여 넣은 내 다른 글 목록(제목·주소·요약)을 견줘, 초안 안에 걸어 둘 만한 글 최대 5개와 넣기 좋은 문단을 알려요. 낱말 모양으로만 맞춰서 뜻만 같은 글은 못 잡아요. 블로그를 직접 읽지 않고, 링크를 넣지 않으며 저장하지 않아요.

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>",
      "posts": "<posts>"
    },
    "name": "blog_internal_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes새 초안 전체(마크다운, 200자 이상)
postsYes내 다른 글 목록(최대 100개). 글마다 title·url·summary(선택 한두 줄)

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?

Annotations already declare readOnlyHint=true and openWorldHint=false; the description goes further by specifying the matching algorithm's limitation, the output cardinality (max 5), and explicitly ruling out blog fetching, link insertion, and saving. That is genuine value beyond the annotations, though it omits anything about ordering, scoring, or confidence of the matches.

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 sentences, each carrying distinct information: what it does, how it matches, what it does not touch. The core action is front-loaded and there is no filler or repetition of the title.

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 covers method, prerequisites, limits, and the non-actions an agent might otherwise assume. The only gap is the shape of the returned candidates (fields per match, whether paragraph positions are offsets or quotes), which an agent cannot infer at all.

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 description coverage is 100%, so both `body` and `posts` (including nested title/url/summary and the 100-item cap) are already documented. The description restates the same field trio and notes the pasted-in nature of the list but adds no formatting, size, or edge-case guidance beyond the schema, so baseline 3 applies.

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: it compares a new draft against the user's pasted post list and returns up to 5 link-worthy posts plus suggested paragraphs. It also states the matching method (surface-form only) and negates adjacent behaviors ('블로그를 직접 읽지 않고, 링크를 넣지 않으며 저장하지 않아요'), so an agent can tell this apart from link-slot or check tools without opening the schema.

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 establishes the prerequisite context clearly — the user must supply their own post list, and the draft should be a full 200+ character markdown body. It also gives a useful when-not signal ('낱말 모양으로만 맞춰서 뜻만 같은 글은 못 잡아요'), but never names or routes to an alternative tool for cases where semantic matching is needed.

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