Skip to main content
Glama

기사 한 건 보기

get_article
Read-onlyIdempotent

기사 번호(idxno)로 한 건을 본다. 제목·기자·발행일·수정일·분야·키워드·앞부분 2,000자와 원문 주소(제휴사 키가 있으면 본문 전체). One BabyNews article by number, with dates and URL.

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": {
      "idxno": "<idxno>"
    },
    "name": "get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
idxnoYes기사 번호

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the description's real contribution is behavioral: it discloses what is returned, that the body is truncated to the first 2,000 characters, and that full text is only available when a partner key is configured. That conditional-access detail is meaningful context an agent could not infer from annotations or schema.

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-loaded with the identifier-based scope, then the return contents. The English sentence largely restates the Korean, which is defensible for bilingual robustness but adds a small amount of redundancy.

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 and a single trivial parameter, the description carries the burden of explaining returns and does so with a concrete field list plus truncation and full-text conditions. The only gap is what happens for an invalid or missing idxno.

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?

Only one parameter with 100% schema description coverage ('기사 번호'), so the schema already carries its meaning; the description restates it without adding format, range, or validity rules. 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?

States a specific verb and resource ('기사 번호(idxno)로 한 건을 본다' — reads one article by number) and enumerates the fields returned, so it is clearly distinguishable from list/search siblings like get_latest_articles or search_articles by virtue of the single-record-by-id scope.

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 phrase 'by article number' implies the caller must already hold an idxno, presumably from a search tool, but the description never says when to prefer this over search_articles or get_related_articles, and there are no exclusions or prerequisites stated.

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.