Skip to main content
Glama

Search Korea Basics

search_korea_basics
Read-onlyIdempotent

한국 여행 안내·관광 통계 (Korea Basics): Search by a few words or a short question. Finds rules and guide pages, travel tool cards, countries, places and collections, and returns the top matches with an id for the other tools and the page URL. Rules, guides and countries match in any language the site uses (English, Korean, Japanese, Chinese, Thai, Russian); places match by their English or Korean name. Use it when it is unclear which tool fits. For festivals and dates use get_korea_dates.

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": {
      "query": "<query>"
    },
    "name": "search_korea_basics"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA few words or a short question, e.g. "K-ETA", "duty free alcohol", "免税", "Gyeongbokgung", "plug adapter".

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 readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavior: per-content-type language matching (any site language for rules/guides/countries, English or Korean only for places) and the shape of the return (top matches with id and page URL). It does not discuss ranking or result limits, which keeps it at 4 rather than 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 purpose, then scope, then routing, then exclusions; nothing is filler. The content-type enumeration and language list make it denser than strictly necessary, but each clause carries usable information.

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 search tool with no output schema, the definition covers input phrasing, language behavior, return contents, and routing. The only gap is result ordering/truncation behavior, which is minor given the 'top matches' framing.

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% and the single parameter is fully documented with examples, so the baseline is a 3. The description adds real meaning beyond the schema by explaining language-matching semantics per result type and by framing the input as 'a few words or a short question', which guides query phrasing.

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 concrete verb and resource ('Search by a few words or a short question') and enumerates what is searchable (rules and guide pages, travel tool cards, countries, places, collections) plus what comes back (top matches with an id and page URL). This differentiates it from siblings like get_korea_topic, find_korea_places, and get_korea_dates without needing to open any schema.

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 when-to-use condition ('Use it when it is unclear which tool fits') and an explicit when-not with the alternative named ('For festivals and dates use get_korea_dates'). The agent has a clear routing rule for the ambiguous-query case.

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