Skip to main content
Glama

WIA GIL: hotels, places, travel basics

Country travel basics (WIA GIL)

gil_country_travel_info
Read-onlyIdempotent

Basic travel info for a country (ISO alpha-2): currency, voltage/plug, time zone, emergency numbers, entry/visa status for Republic of Korea passport holders, and the Korean embassy there. Includes a data_as_of date and disclaimer; may be out of date. (국가별 기본 여행 정보, 한국 여권 기준, 기준일 표시)

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": {
      "country_code": "<country_code>"
    },
    "name": "gil_country_travel_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
country_codeYes2-letter country code, e.g. JP

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 this a safe, idempotent, closed-world read, so the bar is lower; the description still adds genuinely useful behavior: a data_as_of date, a disclaimer, and an explicit warning that the data may be out of date. It also discloses the Korean-passport bias of the visa field, which annotations could never convey.

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-loads the resource and scope in one dense sentence, with the freshness caveat in the same breath. The trailing Korean translation is redundant for an English-reading agent but plausibly aids matching; no filler beyond that.

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 usefully enumerates the returned fields and flags the staleness caveat, which is what an agent needs to set expectations. Given the tool's simplicity, nothing material is missing.

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?

Only one parameter and schema description coverage is 100% ('2-letter country code, e.g. JP'), so the schema does the work. The description's '(ISO alpha-2)' is a marginal restatement rather than added syntax or validation meaning, matching the baseline 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?

Enumerates exactly what the tool returns for a country keyed by ISO alpha-2 code (currency, voltage/plug, time zone, emergency numbers, visa status, embassy), which cleanly separates it from the hotel/places/route/exchange siblings. The retrieval verb is only implicit in 'Basic travel info', but the resource and scope are unambiguous.

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 rather than stated — an agent can infer it should call this when a user needs country-level travel basics. The important qualifier that visa/entry status is scoped to Republic of Korea passport holders is surfaced, which is real guidance, but there is no explicit when-to-use-vs-alternatives or exclusion.

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