Skip to main content
Glama

Builderlog

글감 위험 점검

blog_topic_risk
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": {
      "topics": "<topics>"
    },
    "name": "blog_topic_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
todayNo기준일 YYYY-MM-DD(선택, 기본 오늘 한국 날짜)
topicsYes점검할 글감·제목 후보(최대 10개)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with them while adding real context: it returns warning sentences only and stores nothing. It also discloses the upstream limitation that official announcements are not verified, which prevents the agent from over-trusting a clean result. The remaining gap is the exact shape of the warning output when nothing is found.

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 with the detection scope first, then the limitation, then the return behavior. Every sentence adds distinct information and there is no filler.

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

Completeness5/5

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

With only two parameters, full schema coverage, and no output schema, the description compensates well: it explains what is checked, what is explicitly out of scope, and that only warnings are returned without saving. Nothing an agent needs to call it correctly is missing.

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 parameters and the today default of the Korean date are already documented in the schema. The description mentions the kinds of text that go into topics but adds no syntax, matching rules, or examples beyond what the structured field provides. Baseline 3 is appropriate.

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 states a specific verb and resource: checking blog topics/keywords/title candidates for rumor-style or unannounced expressions and already-passed dates. It also names the detection method (word and date patterns), which is concrete. It does not differentiate itself from siblings such as blog_title_check or blog_check by name, so it stops short of 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 Guidelines3/5

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

The scope boundary 'does not verify official announcement status' implicitly tells the agent what this tool will not do, which is useful. However, there is no explicit guidance on when to choose this over blog_title_check or blog_check, and the pre-publish use context is only implied.

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