Skip to main content
Glama

KOREA WAVE NEWS

Korean culture & travel guide

search_korea_guide
Read-onlyIdempotent

Search Q&A guides on K-drama and filming locations, Korean food, K-beauty, Seoul fashion, Korean expressions, Korea travel tips and tourist places. Returns matching Q&A pairs with page URLs.

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

Input Schema

NameRequiredDescriptionDefault
langNoko or en (default ko)
limitNoNumber of results (default 5, max 10)
queryYesQuestion or keywords
categoryNodrama, food, beauty, fashion, korean, travel (practical tips), places (tourist spots), or any (default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 adds one genuinely useful piece of behavioral context that the annotations lack: the return shape, matching Q&A pairs with page URLs. It says nothing about ranking, result quality, or empty-result behavior.

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 sentences, front-loaded with the verb and scope, then the return format. The topic enumeration is long but each item earns its place by signaling a supported category; no filler or restated title.

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 simple four-parameter, read-only search tool with full schema coverage and no output schema, the definition covers what it searches, what it returns, and its topical bounds. The main residual gap is sibling routing, which matters here because several other search tools exist.

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 coverage is 100%, so every parameter (query, category, lang, limit) is already documented with defaults and enum meanings. The description's topic list loosely parallels the category enum but adds no syntax, matching behavior, or format detail beyond what the schema states, so the baseline of 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 guides) and enumerates the topical scope: K-drama/filming locations, food, K-beauty, fashion, Korean expressions, travel tips, tourist places. This implicitly separates it from search_kpop_guide, but the description never names that sibling, so the agent must infer the boundary from topic coverage alone.

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 by the topical enumeration: an agent learns this tool covers Korean culture/travel Q&A, which suggests when to reach for it. There is no explicit when-not guidance and no named alternative among search, search_kpop_guide, or search_qa, so the choice between siblings is left 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