Skip to main content
Glama

Before-you-fly check for a country

country_entry_check
Read-only

Get the Global TripX before-departure page for a country (entry/visa notes, travel advisories, health notes from Korean public data). Give a country name in any language.

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": "<country>"
    },
    "name": "country_entry_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the page: ko, en or ja (default: guessed from the country name). The 199-country check page is fullest in ko.
countryYesDestination country name in any language (e.g. "Vietnam", "베트남", "ベトナム")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / country / description
      Added value: +"Destination country name in any language (e.g. \"Vietnam\", \"베트남\", \"ベトナム\")"
    • addedInput schema / properties / lang / description
      Added value: +"Language of the page: ko, en or ja (default: guessed from the country name). The 199-country check page is fullest in ko."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish this as a safe, read-only, non-destructive operation, so the description's job is to add context, which it does: it identifies the data source (Korean public data) and notes that the page is fullest in Korean. It omits return-shape details and what happens for unrecognized countries, keeping it below a 5.

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?

The description is two tight sentences with the purpose front-loaded and no filler. The trailing input instruction is slightly redundant with the schema, but it costs 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?

For a simple two-parameter read-only fetch with no output schema, the description covers the source, scope, and input expectations. Minor gaps remain, such as how the response is structured or how missing country data surfaces; they are not critical, because annotations carry the safety profile.

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%, so both parameters, including the lang enum and the default behavior, are already documented. The description's 'in any language' note largely repeats the country parameter's own schema text, so it adds little beyond it. A baseline 3 is appropriate.

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 uses a specific verb and resource ('Get the Global TripX before-departure page for a country') and enumerates the page's contents: entry/visa notes, travel advisories, and health notes. That is enough to distinguish it from sibling names like ask_tripx and search_tripx_guides, though it never explicitly contrasts itself with them.

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?

'Before-you-fly check' and 'Give a country name in any language' imply the usage context: pre-trip country research. However, the description names no alternatives and no when-not conditions, so an agent must infer that this tool should be preferred over the sibling search and Q&A tools when a per-country fact sheet is needed.

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