Skip to main content
Glama

Q&A 한 건 보기

get_qa
Read-onlyIdempotent

Q&A 주소 끝말(slug)로 한 건을 본다. 질문·바로 답·설명·체크리스트·주의·공식 출처. One BabyNews Q&A by slug with answer, checklist and official source.

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": {
      "slug": "<slug>"
    },
    "name": "get_qa"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesQ&A 주소 끝말(slug)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description's added value is enumerating the returned sections (question, direct answer, explanation, checklist, caution, official source), which compensates for the absent output schema. It says nothing about behavior when the slug does not exist, which is the main unaddressed trait.

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?

Very short and front-loaded: purpose first, then the returned components. The Korean and English sentences are near-duplicates, which adds slight redundancy, but total length stays minimal and no sentence is 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?

For a one-parameter read-only lookup, the definition covers purpose, the identifying key, and the shape of the returned content in place of a missing output schema. Only edge-case behavior (unknown slug) is left out, which is minor at this complexity.

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 baseline is 3. The description restates the same meaning ('Q&A 주소 끝말(slug)') without adding format, casing, or sourcing guidance for the slug.

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: fetch a single Q&A item by its URL slug ('Q&A 주소 끝말(slug)로 한 건을 본다'). The singular '한 건' plus slug-based lookup implicitly separates it from search_qa, though it never names that sibling explicitly.

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?

Usage is only implied: the agent must infer that this is the direct-lookup path used when a slug is already known, versus search_qa when only a topic is known. No explicit when-to-use/when-not statement or named alternative is present.

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.