Skip to main content
Glama

Visa Passport Compare

visa_passport_compare
Read-onlyIdempotent

Compare passport power: for 2-5 passports, how many destinations each can enter visa-free / on arrival / with e-visa or eTA / visa required (passport-ranking mobility comparison). With exactly 2 passports, also lists destinations where the requirements differ (up to 30). Data: Passport Index snapshot (2026-02-18). Example: visa_passport_compare({ passports: ["US", "India"] })

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": {
      "passports": [
        "US",
        "India"
      ]
    },
    "name": "visa_passport_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
passportsYes2-5 passports to compare, ISO2, ISO3, or country names, e.g. ["US", "IN"] or ["Germany", "Japan", "Singapore"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / passports / description
      Previous value: -"2-5 passports to compare — ISO2, ISO3, or country names, e.g. [\"US\", \"IN\"] or [\"Germany\", \"Japan\", \"Singapore\"]"New value: +"2-5 passports to compare, ISO2, ISO3, or country names, e.g. [\"US\", \"IN\"] or [\"Germany\", \"Japan\", \"Singapore\"]"
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "passports": [
      +      "US",
      +      "India"
      +    ]
      +  },
      +  {
      +    "passports": [
      +      "Germany",
      +      "Singapore",
      +      "Japan"
      +    ]
      +  }
      +]
  3. First observed

TDQS

A4.1/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 safety is covered. The description adds genuinely useful behavior beyond that: the underlying data source and snapshot date (Passport Index 2026-02-18) and a hard cap of 30 rows for the difference list, which tells the agent results may be truncated.

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 front-loaded with the core action, then the conditional difference behavior, then data provenance and an example. Slightly dense with parentheticals ('passport-ranking mobility comparison') that repeat the obvious, but nothing is wasted enough to hinder parsing.

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 carries the return-value burden and does so: it enumerates the four visa categories and the capped difference list. Only minor gaps remain, such as how unrecognized passport inputs are handled or the shape of per-passport counts versus destination names.

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% and it already documents the 2-5 range, ISO2/ISO3/country-name formats, and examples. The description restates the 2-5 bound and gives one illustration but adds no new semantics such as how ambiguous or unknown country codes are resolved. Baseline 3 is appropriate.

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?

The description states a specific verb and resource ('Compare passport power' for '2-5 passports') plus the exact dimensions compared: visa-free, on arrival, e-visa/eTA, and visa required. It also scopes a second behavior (difference listing) to exactly 2 passports, so an agent can tell precisely what this does that a single-passport lookup would not.

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?

Usage context is clear: use it for 2-5 passports, and the differing-destinations output only applies with exactly 2. That conditional is explicit. It does not name sibling alternatives such as visa_free_destinations or visa_requirement or say when a single-passport lookup is preferable, so the routing guidance stops just short of a 5.

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.