Skip to main content
Glama

Builderlog

링크 자리 점검(제휴 표기·맨 주소·밀도)

blog_link_slot_check
Read-only

초안의 링크를 점검해요. 제휴(수수료) 링크가 있는데 대가 표기가 없거나 링크보다 아래인지, 문장 한가운데 맨 주소가 있는지, 링크가 너무 많은지 봐요. 링크를 열어 보지 않고, 법률 판단이나 글 수정은 하지 않으며 저장하지 않아요.

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

Input Schema

NameRequiredDescriptionDefault
bodyYes초안 전체(마크다운)
has_affiliateNo제휴(수수료) 링크가 있으면 true(알려진 짧은 주소 모양은 자동으로도 봐요)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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, so safety is covered; the description still adds value by stating it does not fetch the links, does not render legal judgment on disclosure, and does not persist anything. Those are real behavioral boundaries an agent would otherwise have to guess at.

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

Conciseness4/5

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

Three short sentences, checks enumerated up front, exclusions batched at the end. No filler; the only mild redundancy is the opening '초안의 링크를 점검해요' restating the name before getting to specifics.

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

Completeness3/5

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

Two simple parameters with full schema coverage and read-only annotations make this a low-complexity tool, which the description mostly matches. But with no output schema, an agent still does not know the shape of the findings returned or the threshold that makes link volume 'too many'.

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 both parameters (body, has_affiliate) are documented in the schema, so the schema carries the load. The description adds only marginal context — that known short-URL patterns are auto-detected — and gives no hint about link-count thresholds or how density is judged.

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?

Names a specific verb (점검) and three concrete checks: missing/misplaced affiliate disclosure, bare URLs mid-sentence, and link density. That is far more specific than the title alone, though it never distinguishes itself from nearby link-related siblings such as blog_internal_links or blog_check.

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

Usage Guidelines3/5

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

Usage is implied (check a draft's links before publishing) and the description gives clear exclusions — it does not open links, make legal judgments, or edit text. However it offers no explicit 'use this instead of X' routing against the sibling tools that also inspect drafts.

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