mcp-server

Visa-Free Destinations by Nationality

list_visa_free_destinations

Read-only

ALL destinations for ONE nationality grouped by requirement: visa-free (with maximum stay days where published), visa on arrival, e-visa, electronic travel authorisation, visa required, no admission - plus the counts and a visa-free-plus-on-arrival mobility total. From the open Passport Index dataset (199 passports); general information, verify before travel.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`group`	No	optional: return only this group
`from_nationality`	Yes	passport held - ISO alpha-2 code or country name

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present only when the request could not be fulfilled.
`terms`	No	Acceptable-use and information-not-advice terms.
`source`	No	Attribution for the data, when it is not Mirabello Consultancy itself.
`book_url`	No	Link to request a consultation with a Mirabello specialist, for a personal case.
`provider`	No	Always "Mirabello Consultancy".
`disclaimer`	No	Information, not legal/tax/financial/immigration advice; figures indicative.
`data_updated`	No	Date the underlying dataset was last updated.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 8, 2026

removedOutput schema / properties / book_a_consultation

Removed value: -{
-  "description": "URL to book a Mirabello consultation.",
-  "type": "string"
-}

addedOutput schema / properties / book_url

Added value: +{
+  "description": "Link to request a consultation with a Mirabello specialist, for a personal case.",
+  "type": "string"
+}

changedOutput schema / properties / source / description

Previous value: -"Attribution for the data."New value: +"Attribution for the data, when it is not Mirabello Consultancy itself."

AddedSep 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's added provenance is the real value: it discloses the Passport Index source (199 passports), the 'where published' caveat on maximum stay days, and a verify-before-travel disclaimer. That is meaningful context beyond the annotations, though it stops short of describing inclusion/counting methodology.

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 scoping and price of the call are front-loaded in a single dense sentence, followed by a short source/disclaimer sentence. The long enumeration of groups is slightly run-on but each clause carries information an agent needs to interpret the output.

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 an output schema present, the description does not need to explain return structure, and it still usefully signals the counts and visa-free-plus-on-arrival mobility total. Combined with the source attribution and travel-verification caveat, an agent has enough to call this correctly; only the routing against sibling visa tools is thin.

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%, so both parameters are already documented in the schema (including the ISO alpha-2-or-name alternation and the group enum). The description adds little parameter-level detail beyond confirming the 'one nationality' constraint, so the baseline 3 applies.

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 names a specific verb and resource ('ALL destinations for ONE nationality grouped by requirement') and enumerates the exact output grouping (visa-free, visa on arrival, e-visa, ETA, visa required, no admission). This distinguishes it from single-pair siblings like check_visa_free and check_visa_requirement without needing to name them.

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

Usage Guidelines3/5

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

The 'ONE nationality' scope and the grouped, whole-list output imply the tool is for bulk mobility breakdowns rather than single-country checks, but no alternative is named and no when-not-to-use condition is stated. Usage must be inferred from scope wording.

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

All mcp-server tools Inspect

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.