Skip to main content
Glama

AllVisas

Does a passport need a visa to visit a country?

check_visa
Read-only

For a short visit (tourism or business): what a passport needs to enter a destination — no visa, an electronic travel authorisation (ETA), an eVisa, a visa on arrival or a visa — read from the destination's own official list, with the verbatim sentence, the official URL and the date it was read. Says plainly when we have not read the destination's list, or when the list does not name the passport.

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": {
      "passport": "<passport>",
      "destination": "<destination>"
    },
    "name": "check_visa"
  }
}

Input Schema

NameRequiredDescriptionDefault
passportYesThe passport's country: name, ISO code or slug, e.g. "India", "IN"
destinationYesThe destination: name, ISO code or slug, e.g. "Japan", "JP"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered; the description goes well beyond that by disclosing provenance (the destination's own official list, verbatim sentence, official URL, and date read) and the failure modes it will report plainly rather than guess. That is exactly the extra context an agent needs to trust and interpret the answer.

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?

Two sentences, scoping first, then the output/provenance guarantee — well front-loaded with no filler. The first sentence is dense with enumerated outcome types, but each element carries information.

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?

For a two-parameter read-only lookup with no output schema, the description covers scope, data source, returned fields and honest-failure behavior. Nothing an agent needs in order to call this correctly or interpret the result 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?

Schema coverage is 100% and both parameters already document accepted forms (name, ISO code, slug) with examples. The description adds no further per-parameter meaning such as what happens with mismatched or unrecognized country inputs, so baseline 3 applies.

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?

States a specific operation on a specific resource: what a passport needs to enter a destination, scoped to short tourism/business visits, and enumerates the possible outcomes (no visa, ETA, eVisa, visa on arrival, visa). That is far more precise than a generic lookup. It stops short of naming a sibling such as search_visas to draw the boundary, so it lands at 4 rather than 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?

'For a short visit (tourism or business)' sets the applicability condition clearly and implicitly excludes long-stay, work or study cases. It gives no explicit alternatives or when-not guidance against siblings like search_visas or get_country, which keeps it below 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.

Resources