Skip to main content
Glama

Visa Requirement

visa_requirement
Read-onlyIdempotent

Do I need a visa? Visa requirement for one passport (nationality) traveling to one destination country, returns visa-free (with allowed stay days when known), visa on arrival, e-visa, eTA, visa required, or no admission. Covers 199x199 country pairs. Data: community-maintained Passport Index snapshot (last updated 2026-02-18), verify with official sources before travel. Example: visa_requirement({ passport: "United States", destination: "Brazil" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "passport": "US",
      "destination": "Brazil"
    },
    "name": "visa_requirement"
  }
}

Input Schema

NameRequiredDescriptionDefault
passportYesPassport / nationality, ISO2, ISO3, or country name, e.g. "US", "DEU", "South Korea", "UK"
destinationYesDestination country, ISO2, ISO3, or country name, e.g. "BR", "Japan", "Türkiye"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / destination / description
      Previous value: -"Destination country — ISO2, ISO3, or country name, e.g. \"BR\", \"Japan\", \"Türkiye\""New value: +"Destination country, ISO2, ISO3, or country name, e.g. \"BR\", \"Japan\", \"Türkiye\""
    • changedInput schema / properties / passport / description
      Previous value: -"Passport / nationality — ISO2, ISO3, or country name, e.g. \"US\", \"DEU\", \"South Korea\", \"UK\""New value: +"Passport / nationality, ISO2, ISO3, or country name, e.g. \"US\", \"DEU\", \"South Korea\", \"UK\""
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "destination": "Brazil",
      +    "passport": "US"
      +  },
      +  {
      +    "destination": "Japan",
      +    "passport": "Germany"
      +  }
      +]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new context: the data provenance (community-maintained Passport Index snapshot dated 2026-02-18), the 199x199 coverage, and an explicit staleness warning to verify with official sources. It does not discuss rate limits or failure behavior for unknown country names, which keeps it from 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?

Front-loaded with the user-facing question, then the precise scope, return categories, coverage, provenance and an example — every sentence carries information. It is dense but not padded; the example call is slightly redundant with the schema examples.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 takes on the burden of describing return values and does so by enumerating the outcome categories (visa-free with stay days, visa on arrival, e-visa, eTA, visa required, no admission). Combined with coverage and data-freshness caveats, an agent has everything needed to call and interpret it.

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% and both parameters already document accepted formats (ISO2, ISO3, country name) with examples. The description only restates the passport-as-nationality meaning and repeats an example call, adding little beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Visa requirement for one passport (nationality) traveling to one destination country') and enumerates the possible outcomes, so an agent knows exactly what it gets back. The 'one passport / one destination' scoping also implicitly separates it from a bulk listing tool like visa_free_destinations.

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?

The single-pair framing plus a concrete example call makes the intended use clear, and the 'verify with official sources before travel' caveat sets expectations. It stops short of explicitly naming an alternative (e.g. visa_free_destinations) or stating when not to use it, so it is clear context without exclusions.

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.