Skip to main content
Glama

Builderlog

AI 말투 점검

blog_ai_tone_check
Read-only

초안에 남은 AI 상투 표현(“결론적으로”, “다양한 …을 통해” 등)·같은 어미 3문장 연속·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>"
    },
    "name": "blog_ai_tone_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes초안 전체(마크다운)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description explicitly says it does not fix or save the article and that it returns warnings plus only the relevant sentence fragments — useful detail about output shape and side-effect scope. It stops short of describing warning format or how many issues may be returned, which keeps it below 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?

Three short sentences, front-loaded with what is detected, followed by the no-mutation guarantee and the return shape. Every sentence carries distinct information and nothing is repeated.

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 single-parameter, read-only check with no output schema, the definition covers detection scope, side effects, and return content — enough to invoke correctly. Only minor gaps remain, such as how warnings are structured or whether long drafts must be trimmed.

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?

There is one parameter with 100% schema description coverage ('초안 전체(마크다운)'), so the schema already does the work. The description's mention of 초안 adds nothing beyond it (no size limits, no note on markdown parsing behavior), matching the baseline 3 for high-coverage schemas.

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?

States a concrete verb (정규식으로 세어요 = count via regex) applied to a specific resource (AI 상투 표현 in a draft), and enumerates the three detectable patterns (cliché phrases, three same-ending sentences in a row, 3-item lists). That is enough to distinguish it from the other blog_check*/blog_voice_profile siblings without naming them, though an explicit contrast is absent.

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 only implied: you run it on a draft to find AI-sounding phrasing. There is no statement of when to prefer this over blog_voice_profile or the other check tools, and no preconditions (e.g., run before or after editing) are given.

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