Skip to main content
Glama

가져오기 (ChatGPT 호환)

fetch
Read-onlyIdempotent

id(art:기사번호 또는 qa:슬러그)로 내용을 가져온다. 기사는 앞부분만(제휴사 키가 있으면 본문 전체), Q&A 는 답과 출처. Fetches one BabyNews article or Q&A by id.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesart:기사번호 또는 qa:슬러그

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: articles return only the leading portion unless a partner key is present, while Q&A returns the answer and its source. That truncation caveat is exactly the kind of context an agent needs before treating the output as complete content.

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?

Two short sentences, front-loaded with the id convention followed by the return-content caveat; nothing is padded. The Korean and English sentences largely duplicate each other, which is defensible for a 'ChatGPT 호환' bilingual tool but is mild 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?

For a one-parameter read tool with annotations and no output schema, the definition covers input format, what content type is returned, and the article-truncation rule. Only minor gaps remain, such as what happens with an unknown or malformed id.

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% with a single required `id` parameter, and the schema description already states 'art:기사번호 또는 qa:슬러그'. The description restates the same prefix convention rather than adding format details, valid slug syntax, or failure behavior, so the 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?

The description names a concrete verb and resource: it fetches exactly one BabyNews item, either an article (art:) or a Q&A (qa:), keyed by id. That is unambiguous. However, it never distinguishes itself from the overlapping siblings get_article and get_qa, so an agent cannot tell from this text why it should choose `fetch` over those.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative routing, even though get_article and get_qa appear to cover the same resources. The id prefix (art: vs qa:) implicitly signals which content type is retrieved, but the agent is left to infer which tool to call and whether a partner key changes eligibility.

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.