Skip to main content
Glama

KOREA WAVE NEWS

List guide topics

list_topics
Read-onlyIdempotent

List KOREA WAVE NEWS guide pages with URLs for a category (kpop, artist, drama, food, beauty, fashion, korean, travel = practical tips, places = tourist spots), to browse what is covered.

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": {
      "category": "<category>"
    },
    "name": "list_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoko or en (default ko)
categoryYesCategory (travel = practical tips, places = tourist spots)

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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is fully covered. The description adds that results include URLs (useful since there is no output schema) but says nothing about result volume, ordering, or pagination for a list operation.

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?

A single front-loaded sentence that leads with the verb and resource before the category detail. The inline enum enumeration is somewhat redundant with the schema and lengthens the sentence, but nothing is wasteful enough to obscure the purpose.

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 two-parameter read-only list tool with full annotation coverage and a fully described schema, the description is sufficient to invoke correctly and notes that URLs are returned. Ordering and pagination behavior are the only meaningful omissions.

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 both parameters enum-constrained, so the baseline is 3. The parenthetical category meanings largely restate the schema's own 'travel = practical tips, places = tourist spots' text, and the optional lang parameter is not mentioned at all, so no net meaning is added.

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?

Names a specific verb and resource ('List KOREA WAVE NEWS guide pages with URLs') and scopes it to a category, so an agent knows exactly what it retrieves. The 'browse what is covered' phrasing suggests a browse-style tool, but it never names a sibling search tool to contrast with, so differentiation is implied rather than stated.

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?

'to browse what is covered' implies a browsing use case versus targeted search, which is useful but only implicit. There is no explicit when-not guidance (for example, when to prefer search_korea_guide or search_kpop_guide for a specific lookup), leaving the agent to infer routing.

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