Skip to main content
Glama

everyone-builder

media_comparison

같은 사건을 한국 매체들이 어떻게 다르게 썼는지 비교해 줍니다. 여러 매체가 함께 다룬 사건을 묶고(우리 계산), 매체별 제목을 나란히 놓고, 제목들이 무엇을 앞세웠는지 분석한 한국어 글을 함께 줍니다(우리가 쓴 글이라 전문을 제공합니다). '이 뉴스 매체별로 어떻게 다르게 보도했어?' 같은 질문에 쓰세요. 다른 곳에서는 얻을 수 없는 자료입니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "media_comparison"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo사건 수 (1~10, 기본 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the disclosure burden. It usefully reveals that grouping is computed server-side and that the analysis text is authored/proprietary with full text provided, implying a read-only content tool. It says nothing about freshness, coverage window, cost, or response latency, which matters for a tool whose value depends on how many events it can aggregate.

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?

Front-loads the essential purpose in a bolded first clause, then layers output detail and a usage trigger. The closing '다른 곳에서는 얻을 수 없는 자료입니다' is promotional filler that doesn't help an agent decide, a minor waste in an otherwise tight three-sentence block.

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 one-parameter read tool with no output schema, the description does the important work of explaining the three returned components and that the analysis is in Korean. It stops short of describing the response structure or ordering, so an agent cannot predict the exact shape, but nothing needed 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 coverage is 100%; the single 'limit' parameter is fully documented as event count (1–10, default 5). The description neither repeats nor adds meaning such as what happens when limit exceeds available grouped events, so it neither helps nor hurts beyond the schema baseline.

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?

States a specific verb+resource: comparing how Korean outlets covered the same event. It goes further than naming the action by describing the output components — grouped events, side-by-side headlines, an analysis of what each headline foregrounded — so an agent knows exactly what it gets back, distinct from a generic news-fetch sibling.

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?

Gives an explicit trigger with a sample user question ('이 뉴스 매체별로 어떻게 다르게 보도했어?'), which is concrete and easy to match against intent. It does not, however, contrast itself with siblings like korea_it_news or today_digest, so an agent must infer that it should prefer those for plain news retrieval.

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