Skip to main content
Glama

대전한콕 Daejeon Hankok

대전한콕 상세 열기

fetch
Read-onlyIdempotent

search 결과 id(p/{category}/{id} 또는 d/{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
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the text. The description adds one genuinely new behavioral fact — that it returns the full detail text rather than a search snippet — but says nothing about failure modes for a malformed or stale id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the input provenance and the id format, with no filler or restatement of the title. Every clause carries information the agent would otherwise have to guess.

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 single-parameter read tool with rich annotations and no output schema, the definition covers input provenance, accepted id formats, and the depth of the returned content. The remaining gap is a brief note on what happens when the id is invalid or expired, which matters for an id-driven lookup.

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 0% and the single parameter is documented only as a bare string, so the description must carry the meaning — and it does, spelling out both accepted id shapes (p/{category}/{id} and d/{id}). That format specification is exactly the information an agent needs and cannot get from the schema.

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 pairs a specific verb (연다/open) with a specific resource (상세 전문, the full detail body) and ties it to an id obtained from search. The id-prefix encoding (p/{category}/{id} vs d/{id}) hints at the entity type, though the description never names what kind of object is being opened. It is clear enough to act on but does not explicitly contrast itself with get_place or get_stylist.

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 implied rather than stated: the phrase 'search 결과 id' signals the intended two-step flow of search first, then fetch by id. There is no explicit when-not guidance and no named alternative for fetching details, so the agent must infer the routing from sibling names alone.

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