Skip to main content
Glama

One rule or guide, summarized

get_korea_topic
Read-onlyIdempotent

한국 여행 안내·관광 통계 (Korea Basics): Answer one question from one Korea Basics page: a rule (K-ETA, duty-free allowance, prohibited goods, medication, tax refund, cash declaration, driving, layover tours and more), a guide (airport arrival, getting around, tourist passes, public holidays), or a travel tool card (plugs, tipping, transit cards, exchange rate, medicine sold at convenience stores). Returns the direct answer, the date it was last checked, and the page URL. Pass about with the thing asked (for example tobacco, alcohol, a medicine ingredient) to get up to three matching lines from the page's tables. For rules that depend on the passport, use get_korea_trip_guide with the country instead. The full tables and the official link for applying are on the page.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe topic id from search_korea_basics or get_korea_basics_overview (e.g. "k-eta", "customs-allowance", "currency-declaration", "transit-tour", "plug-card"), or its name in plain words (e.g. "duty free", "cash declaration", "layover", "tipping"). If unsure, call search_korea_basics first.
aboutNoOptional. The thing asked about, e.g. "tobacco", "alcohol", "zolpidem", "layover".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.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 the safety profile is covered. The description still adds real value beyond them by disclosing the return shape (direct answer, last-checked date, page URL) and by scoping `about` to 'up to three matching lines,' which tells the agent this is a summarized excerpt rather than full tables. It does not say what happens on an unmatched id or an `about` that yields no rows, which keeps it from a 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?

Front-loaded with the core action and one dense but purposeful enumeration of covered topics, which genuinely helps scope judgment. The parenthetical lists are long and the paragraph is unbroken, but no sentence is filler; slightly tighter grouping of the examples would earn a 5.

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 params, no output schema, and rich annotations, the description covers what an agent needs: scope, the alternative for passport-dependent rules, and the return contents. The main residual gap is failure behavior when the id or `about` matches nothing, which matters for a lookup tool with a free-text name fallback.

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 the baseline is 3. The description goes beyond the schema by explaining the effect of `about` (matching lines drawn from the page's tables, capped at three) and by noting that ids may be plain words rather than canonical slugs, which shapes how an agent should populate the argument.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Answer one question from one Korea Basics page,' then enumerates the three content classes (rules, guides, tool cards) with concrete examples so an agent can tell whether its question falls in scope. It also explicitly distinguishes itself from the sibling get_korea_trip_guide for passport-dependent rules.

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

Usage Guidelines5/5

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

Gives an explicit routing rule: use this tool for a rule/guide/tool card, but for rules that depend on the passport, use get_korea_trip_guide with the country instead. It further explains the `about` usage pattern for table lookups, and the schema adds the fallback (search_korea_basics if the id is unknown), leaving little to inference.

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