Skip to main content
Glama

KOREA WAVE NEWS

K-pop concert & idol guide

search_kpop_guide
Read-onlyIdempotent

Answers about K-pop in Korea: concert venues (Gocheok Sky Dome, KSPO DOME, Inspire Arena), ticketing and queues, ID checks, lightsticks, merch, fan culture, idol positions, fancams, music shows, scalping law, trips to Korea for concerts, trot, K-musicals and other live shows. 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_kpop_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoko or en (default ko)
limitNoNumber of results (default 5, max 10)
queryYesQuestion or keywords, e.g. "고척스카이돔 시야", "how to buy concert tickets in Korea"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 safety needs no restating. The description adds genuinely new information by disclosing the return shape: matching Q&A pairs with page URLs, which tells the agent to expect curated answer snippets rather than raw documents.

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 purpose in the first clause, then a scope list, then the return shape. The venue-name parenthetical and topic list are long but each item aids retrieval matching; nothing is filler.

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 three-parameter retrieval tool with no output schema, the definition covers scope, return format and language support adequately. Only the routing relative to the general Korea guide sibling is left implicit.

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%, with query, lang (ko/en enum) and limit (1-10, default 5) all documented inline including example queries. The description adds nothing about parameters, so the schema carries the full load — the correct baseline of 3.

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 and resource — answers questions about K-pop in Korea — and enumerates the concrete subject matter (venues, ticketing, ID checks, lightsticks, fancams, scalping law, trot, K-musicals). The scope is unmistakable, though it never names a sibling like search_korea_guide or search_qa to sharpen the boundary.

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?

The topic enumeration implicitly draws a scope line (K-pop/live shows vs. general Korea questions), so an agent can infer this is the fan-culture vertical rather than a general search. There is no explicit when-to-use or when-not-to-use statement and no routing to the general guide or QA siblings.

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