Skip to main content
Glama
Sign In

orizn-visa-mcp

by io.github.MattJeff
OverviewDiscussionsAdmin

Full visa requirements

check_visa_requirement
Read-onlyIdempotent

[needs a free API key — this call will fail without one: https://visa.orizn.app/visa-api/register?source=mcp-remote, then reconnect with ?key=] THE default visa tool: the full entry record for ONE passport travelling to ONE destination. Returns the requirement (visa_free / visa_required / e_visa / visa_on_arrival / eta / no_admission), days allowed, a written description, required documents, application steps, visa types, cost, validity, max stay, processing time, passport validity months, visa fees, photo specs, vaccinations, insurance, safety advisory, health requirements, overstay penalties, entry by mode (air/land/sea), transit rules, remote-work visa, extension rules, minor rules, dual-nationality and passport-stamp warnings, and embassies — in any of 15 languages, on every plan including free (fr, en, es, pt, de, ja, ko, zh, ru, it, ar, hi, th, vi, tl). Call it whenever the user asks whether they need a visa, what documents or vaccinations are needed, what a visa costs, how long it takes, how long they can stay, or what happens if they overstay. Needs an Orizn API key on this MCP connection and costs 1 request against that key's monthly quota. On the free plan the deep fields come back as {upgrade: "Available on Starter plan or above"} instead of data — report that as a plan limit, never as missing data. Reading the reply: every deep field carries a granularity. "destination" means the value describes the destination country for all nationalities (fees, processing days, transit, overstay, safety); "passport" means it describes the passport for all destinations (reciprocity history, stamp and dual-nationality warnings). Only the requirement, visa-free days, description and documents are pair-specific. A field Orizn does not have comes back as {status: "unavailable"} — say so rather than filling the gap, and as_of is the reference date of that field, not live data.

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_requirement"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the written fields. One of: fr, en, es, pt, de, ja, ko, zh, ru, it, ar, hi, th, vi, tl. Defaults to en. Available on every plan, free included.
passportYesPassport country, ISO 3166-1 alpha-3 (e.g. FRA for France).
destinationYesCountry being entered, ISO 3166-1 alpha-3 (e.g. JPN for Japan).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare read-only/idempotent/open-world; the description goes far beyond, disclosing the API-key prerequisite with a registration URL, the 1-request quota cost, the free-plan {upgrade: ...} masking behavior and how to report it, the granularity semantics of deep fields, and the {status: 'unavailable'} / as_of conventions. These are exactly the non-obvious traits an agent needs before calling.

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?

Structurally front-loaded: key requirement, default status, payload, and call triggers precede the 'reading the reply' guidance. It is dense but nearly every clause carries operational information; the main cost is some repetition (the language list appears twice) and a long single block.

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 carries the return-value burden and does so thoroughly — enumerating fields, explaining granularity, free-plan masking, and unavailability markers. An agent can interpret the response correctly without further documentation.

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%: passport/destination ISO codes and the lang enum are fully documented in the schema, so the baseline of 3 applies. The description restates the 15-language support but adds no format or constraint detail beyond the schema.

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 ('full entry record for ONE passport travelling to ONE destination') and explicitly claims the default slot against siblings like check_transit_visa and quick_visa_check. The enumerated return fields make the tool's scope unmistakable.

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?

Provides a concrete trigger list ('whenever the user asks whether they need a visa, what documents or vaccinations...'), which leaves little inference. It does not, however, explicitly name when to prefer quick_visa_check, check_transit_visa, or compare_destinations, so routing among siblings is only partly covered by the 'THE default' framing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All orizn-visa-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources