Skip to main content
Glama

KOREA WAVE NEWS

Search Korea culture & travel Q&A

search_qa
Read-onlyIdempotent

Search Q&A and travel guides about Korea (opening hours, admission, parking, K-ETA, transport, food, culture). Answers are from public sources; check the source before travelling.

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_qa"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoqa = place Q&A, guide = travel guide, any = both (default)
langNoLanguage code. Default ko. If the content is not available in that language, results fall back to the languages that exist.
limitNoNumber of results (default 5, max 10)
queryYesQuestion or keywords

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description does add one piece of non-annotation context — that answers come from public sources and should be verified before travel — which is a meaningful data-provenance caveat. It says nothing about result shape, ranking, or coverage limits.

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 compact sentences, front-loaded with the resource and scope, with no redundant restatement of the title. The topic parenthetical is slightly long but earns its place by signalling matchable query domains.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A read-only search tool with a fully documented 4-parameter schema is mostly self-sufficient, but there is no output schema and the description never indicates what a result contains (title, snippet, source URL, language) or how limit interacts with ranking. That leaves an agent guessing about the return shape.

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 description coverage is 100% and both enums (kind, lang) are already documented in the schema, including fallback behavior for lang. The description adds no syntax, examples, or meaning beyond that, 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?

States a specific verb (Search) and resource (Q&A and travel guides about Korea), and the topic parenthetical (opening hours, admission, parking, K-ETA, transport, food, culture) makes the domain concrete. It does not distinguish itself from plausible siblings such as search_korea_guide, so an agent cannot tell from this text alone which search to pick.

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?

No when-to-use or when-not-to-use guidance and no named alternative, even though sibling tools with overlapping names (search, search_korea_guide, search_kpop_guide) exist. The only usage-adjacent statement is the caveat to check sources before travelling, which is about result trust, not tool selection.

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