Skip to main content
Glama

Builderlog

블로그 제목 점검

blog_title_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": {
      "title": "<title>"
    },
    "name": "blog_title_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo글 종류: general 일반 정보 · howto 사용법·설정 · money 돈·세금·계산 · it IT·제품 가격 · entertainment 방송·연예 리뷰 · review 제품 후기(직접 써 본 것) · visit 방문 후기(맛집·장소, 직접 가 본 곳)
titleYes점검할 제목 한 줄
keywordNo검색 키워드(선택, 제목 앞 12자 안에 있는지 봐요)
past_titlesNo이미 올린 내 글 제목들(겹침 확인, 선택)

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces this with concrete scope: it returns only a fix/recommendation list and never edits or persists the title. It also discloses the internal rule categories being applied, which is behavioral detail the annotations cannot express. It does not describe output structure or limits, which keeps it from 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. The positive capability with its rule list comes first, the no-mutation guarantee second, which is the right order for an agent scanning for fit.

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?

With no output schema, the description carries the return-value burden and does so at a high level ('고칠 것과 권함 목록만'), which is enough to set expectations for a diagnostic call. A slightly fuller note on what each returned item contains would close the remaining gap.

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%, including the enum meaning for 'kind' and the 12-character keyword window, so the schema already carries the parameter burden. The description mentions keyword position and past-title overlap but adds no syntax or constraints beyond what the schema states; baseline 3 applies.

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 specific verb and resource ('네이버 블로그 글 제목 한 줄을 규칙으로 점검') and enumerates the exact rule set it applies (character cap, keyword position, exaggerated/vague wording, overlap with past titles), so the agent knows precisely what the tool evaluates. It stops short of naming how it differs from near-neighbors such as blog_dup_check, which also touches title overlap.

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: the checks described make clear this is a pre-publish title review, and the negative statement ('제목을 바꾸거나 저장하지 않아요') implies it is a diagnostic, not a fixer. There is no explicit when-to-use/when-not-to-use guidance or routing to an alternative for duplicate-checking or tone-checking.

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