Skip to main content
Glama

What to do before, on arrival, during the stay, and before leaving

get_korea_trip_guide
Read-onlyIdempotent

한국 여행 안내·관광 통계 (Korea Basics): List what a visitor has to deal with at one stage of a trip to Korea (before, arrival, stay, departure, or all): each rule with its value as the government document states it, whether something is filed online in advance, the check date, and the page URL. With a country, the values that depend on nationality (visa-free stay, K-ETA, automated immigration lanes) are for that passport. With an arrival date and nights, values are the ones in force on that date, and the result adds the public holidays and festivals that fall in the stay. The arrival stage includes the order of the counters at the airport. Values only, no decision about a person's eligibility.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_korea_trip_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
stageNoOptional. Defaults to all.
nightsNoOptional length of stay in nights, used with arrival_date.
countryNoOptional passport country: a country name in any of the site's languages or an ISO code, e.g. "Japan", "日本", "US", "DEU".
arrival_dateNoOptional arrival date, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. Beyond that, the description discloses that results carry source-of-truth rule values, a check date, page URLs, added public holidays/festivals for dated stays, and airport counter order for the arrival stage, which is useful behavioral context. It does not discuss pagination or result size.

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?

It is front-loaded with the core action and stage scope, then adds conditional clauses. It is dense but nearly every clause carries information. The parenthetical Korean/English label adds little.

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 must explain return values, and it does: per-rule values, online-filing status, check date, page URL, plus holidays when dates are given. It also discloses the eligibility boundary. It largely covers correctness needs, with minor gaps around result volume.

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%, so the baseline is 3. The description does add conditional meaning beyond the schema: country selects nationality-dependent values (visa-free stay, K-ETA, automated lanes), and arrival_date plus nights switch to in-force values and add seasonal events. That extra conditional logic is the main value it adds to the parameters.

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 states a specific verb and resource: it lists what a visitor must handle at one stage of a Korea trip, with the government-stated rule value, online-filing flag, check date, and page URL. The purpose is clear, but the description never names or contrasts the sibling tools (for example, get_korea_basics_overview or search_korea_basics), so an agent must infer how this tool differs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear conditional usage: pass a country to get nationality-dependent values, and pass arrival_date with nights to get the values in force on that date plus in-stay holidays and festivals. It also sets a boundary ('Values only, no decision about a person's eligibility'). It does not say when to use it instead of the sibling overview or search tools.

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