Skip to main content
Glama

Visa Free Destinations

visa_free_destinations
Read-onlyIdempotent

Where can holders of a given passport travel without a visa? Lists every destination grouped by requirement: visa-free (with allowed stay days), visa on arrival, e-visa, eTA, plus counts for visa-required and no-admission. Optional filter to a single category. Answers "visa-free countries for X passport holders". Data: Passport Index snapshot (2026-02-18). Example: visa_free_destinations({ passport: "Germany" })

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": "Germany"
    },
    "name": "visa_free_destinations"
  }
}

Input Schema

NameRequiredDescriptionDefault
passportYesPassport / nationality, ISO2, ISO3, or country name
requirementNoOptional: return only destinations in this category (default: full lists for visa_free, visa_on_arrival, e_visa, eta, plus counts for the rest)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / passport / description
      Previous value: -"Passport / nationality — ISO2, ISO3, or country name"New value: +"Passport / nationality, ISO2, ISO3, or country name"
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "passport": "Germany"
      +  },
      +  {
      +    "passport": "India",
      +    "requirement": "visa_free"
      +  }
      +]
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuine value beyond them by disclosing the underlying data source and snapshot date (Passport Index, 2026-02-18), which tells the agent the answers may be stale. It does not add page-size, result-volume, or rate-limit context, so it sits at a solid 3.

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 user-shaped question, then the response breakdown, filter note, provenance, and example – a logical order. Nearly every clause is load-bearing, though the opening question and the closing quoted phrasings restate the same intent and could be tightened by a sentence.

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

Completeness3/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 does a good job explaining what comes back (grouped lists, allowed stay days, counts for excluded categories) and records the data vintage. It leaves some ambiguity, though: an agent cannot tell whether visa-free destinations include stay-day ranges per country, how large the result set is, or whether missing passports are reported as errors or empty results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the schema already documents both the passport identifier formats and the requirement enum default behavior. The description reinforces the practical effect of the filter ("plus counts for visa-required and no-admission" when unfiltered) and supplies two example invocations, which clarifies intent without duplicating the schema verbatim.

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 names a concrete operation on a concrete resource: it answers "Where can holders of a given passport travel without a visa?" and enumerates the exact output grouping (visa-free with stay days, visa on arrival, e-visa, eTA, plus counts). Its scope – all destinations for one passport, not a single passport/destination pair – implicitly separates it from a pairwise check like visa_requirement, but it never names that sibling, so it stops short of a 5.

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 context for use ("Answers 'visa-free countries for X passport holders'") and shows when to add the narrowing filter ("Optional filter to a single category") with a worked example call. It offers no exclusions, however – it never says to use visa_requirement instead when only one passport/destination pair is in question.

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.