Skip to main content
Glama

Quick visa check

quick_visa_check
Read-onlyIdempotent

Does this passport need a visa for this destination? Returns the requirement, the number of visa-free days, and — when that exact pair has been individually re-verified — the date it was. One pair per call, English only. Prefer it when the user wants a plain yes/no; switch to check_visa_requirement as soon as they need documents, fees, processing times, transit rules, or an answer in another language. Works with NO API key, 10 checks per day per network — the only tool that answers a traveller's question keyless. With a key it costs 1 request. Free API key: https://visa.orizn.app/visa-api/register?source=mcp-remote — 100 requests/month, no card, and it unlocks documents, fees, processing times, transit rules and 15 languages. Then reconnect with the key: https://visa.orizn.app/mcp?key=, or an Authorization: Bearer header.

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": "quick_visa_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
passportYesPassport country, ISO 3166-1 alpha-3 (e.g. FRA)
destinationYesDestination country, ISO 3166-1 alpha-3 (e.g. JPN)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, but the description adds non-obvious operational facts: it works with no API key, is capped at 10 checks per day per network, and costs 1 request with a key. It also discloses the English-only and one-pair-per-call limitations, which are genuine behavioral constraints beyond the annotations. The remaining registration/reconnect copy is promotional rather than behavioral.

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 selection-critical content (purpose, return values, alternative, limits) is front-loaded in the first four sentences. The trailing API-key registration and reconnect URLs are longer than needed for the tool's call semantics, though they partly serve the keyless-limit disclosure.

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-param lookup with no output schema, the description covers what comes back, the exact scope (one pair, English), the rate limit and auth model, and the sibling to escalate to. An agent has everything needed to decide and call correctly.

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 coverage is 100% and both params carry ISO 3166-1 alpha-3 examples, so the baseline is 3. The description still adds value by stating "one pair per call" and "English only," constraining how the two params may be used in a way the schema does not express.

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?

Opens with a specific question form ("Does this passport need a visa for this destination?") that states verb, resource and both inputs, then names exactly what is returned (requirement, visa-free days, re-verification date). It explicitly contrasts itself with check_visa_requirement, so an agent can separate the two without reading either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit selection rule: prefer this for a plain yes/no, switch to check_visa_requirement once documents, fees, processing times, transit rules or another language are needed. The alternative is named and the switching condition is concrete, leaving nothing to inference.

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.