mcp-server

Fastest Route to Citizenship by Nationality

find_fastest_citizenship

Read-only

Naturalisation periods and NATIONALITY-BASED FAST TRACKS, verified against the enacted statute. Pass nationality (ISO-3166 alpha-2 of the passport held) to rank covered jurisdictions by how soon THAT nationality may apply for citizenship — e.g. an Ibero-American national reaches Spanish citizenship in 2 years instead of 10 (Codigo Civil art. 22.1), a CPLP national reaches Portuguese citizenship in 7 instead of 10 (Lei 37/81 art. 6 as amended by Lei Organica 1/2026), a Samoan citizen lawfully resident in New Zealand has an immediate entitlement with no presence test at all (Citizenship (Western Samoa) Act 1982 s 7(1)). Pass cc instead for one jurisdiction in full, including the ordinary baseline, who gets NO reduction, and any transitional regime. Periods are qualifying residence before an application may be made and exclude processing time. Coverage is narrow by design — a jurisdiction appears only once its statute has been read in full, so absence means unverified, never that no fast track exists.

Input Schema

TableJSON Schema

Name	Required	Description
`cc`	No	ISO-3166 alpha-2 of the destination jurisdiction, e.g. ES, PT, NZ, AU
`bloc`	No	Limit the ranking to one bloc, e.g. EU for "fastest EU passport". One call returns every covered member ranked, with presence and requirements, plus the members not yet covered.
`nationality`	No	ISO-3166 alpha-2 of the passport held, e.g. BR, AR, WS, NZ

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."

Changed1 schema field changedSep 24, 2026

addedInput schema / properties / bloc

Added value: +{
+  "description": "Limit the ranking to one bloc, e.g. EU for \"fastest EU passport\". One call returns every covered member ranked, with presence and requirements, plus the members not yet covered.",
+  "enum": [
+    "EU",
+    "EEA",
+    "FREE_MOVEMENT"
+  ],
+  "type": "string"
+}

AddedSep 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds substantial context beyond that: periods are qualifying residence excluding processing time, coverage is narrow by design with absence meaning 'unverified, never that no fast track exists', and entries are verified against enacted statutes. These are meaningful behavioral and provenance disclosures.

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?

Front-loaded with the core purpose, then parameter behavior, then coverage caveats. Dense and largely waste-free, though the parenthetical legal citations make the sentence long; still, each clause carries informational value.

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 zero-required-param, three-parameter read tool with an output schema present, the description covers everything an agent needs: what each parameter produces, the meaning of the returned periods, and the coverage caveat. Return-value explanation is rightly left to the output schema.

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%, so the baseline is 3. The description nonetheless adds real meaning: it explains the distinct behavior of each parameter (nationality ranks, cc returns one jurisdiction in full including who gets no reduction, bloc ranks a bloc with presence and requirements plus uncovered members). This goes beyond the schema's format hints.

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+resource (rank jurisdictions by how soon a given nationality may apply for citizenship) and scopes it with concrete examples (Ibero-American → 2 years in Spain, CPLP → 7 in Portugal, Samoan → immediate in NZ). It is clearly distinguishable from siblings like find_pathways and check_eligibility, which concern eligibility rather than nationality-based fast-track ranking.

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?

Gives explicit parameter-selection guidance: pass nationality to rank, pass cc for one jurisdiction in full including baselines and transitional regimes, pass bloc for a bloc ranking. It also clarifies the coverage policy (absence means unverified). It stops short of naming sibling alternatives or when-not-to-use conditions, so not a full 5.

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.