Skip to main content
Glama

Holidays, festivals and seasons

get_korea_dates
Read-onlyIdempotent

한국 여행 안내·관광 통계 (Korea Basics): List dates in Korea: public holidays, festivals and events, or seasonal dates (autumn foliage, cherry blossom, beach opening, winter). Returns up to 30 dated lines from the start date with the check date and the page URL. Seasonal dates state which year they are from. Events are listed only once announced.

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": {
      "kind": "<kind>"
    },
    "name": "get_korea_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional end, YYYY-MM-DD or YYYY-MM.
fromNoOptional start, YYYY-MM-DD or YYYY-MM. Defaults to today in Korea.
kindYesWhat to list.
regionNoOptional. For events, the province; for seasons, the dates for places in that region. e.g. "Seoul", "Busan".

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 read-only, idempotent, non-destructive and closed-world behavior, so the description's job is to add operational detail, and it does: a 30-line cap starting from the start date, inclusion of a check date and page URL, year attribution on seasonal dates, and the announcement-lag caveat for events. It stops short of covering pagination or how to retrieve results beyond the cap.

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 resource and kinds, then a compact set of operational facts in two sentences. The Korean/English category label adds slight noise but nothing is padded or repeated.

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 supplies return-shape information (dated lines, check date, URL, year attribution) that the agent otherwise would not have. For a simple filtered-list tool with fully documented parameters, this is close to complete; only result-window/tail behavior 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 coverage is 100% with each parameter documented, so the schema carries the parameter burden. The description adds only that 'from' acts as the start of the returned window and that 'region' scopes events vs. seasonal places in a limited way, which is marginal beyond the schema baseline.

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: lists dated items in Korea (public holidays, festivals/events, or seasonal dates) with concrete examples for each kind. It is clear on its own, though it does not explicitly separate itself from sibling guides such as get_korea_trip_guide or get_korea_topic.

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 implied by the kind enum and by caveats like 'Events are listed only once announced', which tells the agent not to expect unannounced events. There is no explicit when-to-use vs. when-not-to-use guidance or routing to an alternative (e.g. trip guide for planning narrative), so it stays at implied usage.

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