Skip to main content
Glama

everyone-builder

korea_it_news

한국 IT·AI 뉴스의 최신 제목을 매체·링크와 함께 돌려줍니다. 20여 개 한국 IT 매체의 공개 RSS 를 모은 것으로, 한 매체가 목록을 독점하지 않게 섞어 줍니다. 본문은 제공하지 않습니다 — 반드시 원문 링크를 함께 보여 주세요. query 를 주면 그 말이 든 기사를 찾습니다 (예: '엔비디아', '오픈소스 LLM').

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": "korea_it_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo돌려받을 개수 (1~30, 기본 15). 넘기면 30에서 잘립니다
queryNo찾을 말. 비우면 최신순

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?

No annotations exist, so the description carries the full burden, and it delivers: sources are ~20 public Korean IT RSS feeds, results are interleaved so no single outlet dominates, and body text is deliberately not returned. It does not cover freshness/latency or failure behavior when a feed is down, which keeps it below 5.

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?

Four short sentences, front-loaded with what is returned before the aggregation and no-body caveats. Every sentence carries information; the only minor drag is that the 'always show the original link' instruction is more of an output convention than tool description.

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 only two optional parameters and no output schema, an agent needs to know the payload shape and its limits; the description supplies that (titles plus outlet and link, no body text, capped result count) and warns against monopolizing single sources. Missing only edge-case behavior when a source is unavailable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented and the baseline is 3. The description earns the extra point by giving concrete query examples ('엔비디아', '오픈소스 LLM') and clarifying that an empty query yields newest-first ordering, which shapes how an agent should fill the field.

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: returns the latest Korean IT/AI news titles together with outlet and link, aggregated from ~20 public RSS feeds. That is concretely distinct from siblings like media_comparison or today_digest, though the description never names an alternative to contrast with.

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?

It explains the query parameter's search behavior with concrete example terms and instructs the agent to always surface original links, which is genuine usage context. However, it never says when to pick this over today_digest or media_comparison, so routing guidance is only implied by the topical scope.

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