Skip to main content
Glama

Where visitors go in Korea

get_korea_visitor_stats
Read-onlyIdempotent

한국 여행 안내·관광 통계 (Korea Basics): Monthly figures on where people go in Korea, from official statistics: where international visitors go, where Koreans go on weekends, places both go, places Koreans go and international visitors rarely do, places international visitors go and Koreans less so, the most-entered paid attractions, what changed most, arrivals by nationality, one province, or one district. Returns the top 10 lines with what the number means and its month, and the page URL for the full ranking, map and trend. Figures only, no recommendation.

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": {
      "view": "<view>"
    },
    "name": "get_korea_visitor_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYesWhich figures. "region" needs region; "place" needs place (a district).
monthNoOptional. YYYY-MM or "latest".
placeNoFor view "place": a district or a neighbourhood or place inside it, e.g. "Jongno-gu", "Haeundae", "Myeongdong".
regionNoFor view "region": a province or metropolitan city, e.g. "Busan", "Jeju".

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 read-only, idempotent, non-destructive, closed-world reads, so the safety profile needs no restating. The description does add real behavioral context beyond that: results are capped at the top 10 lines, each line carries the figure's meaning and month, and a page URL is returned for the full ranking, map and trend. It does not say how fresh the statistics are or what happens with an invalid/missing region or place.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core statement is front-loaded, but the middle is one long comma-chained enumeration of views that reads as a run-on and partially duplicates the enum in the schema. The bilingual header ('한국 여행 안내·관광 통계 (Korea Basics)') adds context but also bulk without operational value.

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?

With no output schema, the description carries the burden of describing returns, and it does: top 10 lines, meaning of the number, month, and a URL to the full ranking/map/trend. Combined with full schema coverage and clear annotations, an agent has enough to call this correctly; only data vintage and error behavior are unaddressed.

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%, so the baseline is 3; the description earns an extra point by translating several enum values into plain language (where Koreans go on weekends, places both go, places international visitors rarely do, most-entered paid attractions, what changed most) and by linking the 'one province' and 'one district' cuts to the region/place parameters. It does not add format detail for month beyond what the schema states.

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?

The description names a concrete resource (monthly official statistics on where international visitors and Koreans go in Korea) and enumerates the specific cuts available: arrivals by nationality, single province, single district, top paid attractions, biggest changes. An agent can tell this is a statistics-lookup tool rather than a guide or place-search tool, though it never names a sibling to contrast with.

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?

"Figures only, no recommendation" usefully signals this is not a planning/advice tool and hints at a boundary with guide-type siblings, but there is no explicit when-to-use or when-not-to-use rule and no named alternative for related questions. Usage must be inferred from the view list.

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