mcp-server

Find Immigration Pathways

find_pathways

Read-only

Find which countries offer a given immigration pathway (e.g. digital-nomad, skilled-work, ancestry-descent, retirement-passive, eu-free-movement). Returns the screened countries that have it, each with its key requirements (income thresholds included), cost and path to PR. EU/EEA/Swiss citizens moving within the EU/EEA or Switzerland use eu-free-movement, not a visa.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`region`	No	Region filter, matched case-insensitively (e.g. "Caribbean", "EU", "Middle East", "Pacific", "Africa", "Asia").
`pathway`	Yes	Pathway id. eu-free-movement = living in another EU/EEA state or Switzerland as an EU/EEA/Swiss citizen.

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.
`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.
`book_a_consultation`	No	URL to book a Mirabello consultation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 24, 2026

changedInput schema / properties / pathway / description

Previous value: -"Route family to filter on (e.g. \"donation\", \"real_estate\", \"business\", \"bonds\")."New value: +"Pathway id. eu-free-movement = living in another EU/EEA state or Switzerland as an EU/EEA/Swiss citizen."

addedInput schema / properties / pathway / enum

Added value: +[
+  "eu-free-movement",
+  "retirement-passive",
+  "digital-nomad",
+  "skilled-work",
+  "general-work",
+  "startup-entrepreneur",
+  "talent-exceptional",
+  "study",
+  "family-reunification",
+  "marriage",
+  "ancestry-descent",
+  "naturalisation-ordinary",
+  "invest-residence",
+  "invest-citizenship"
+]

removedInput schema / properties / pathway / examples
```
Removed value: -[
-  "real_estate"
-]
```

Changed4 schema fields changedSep 23, 2026

addedInput schema / properties / pathway / description

Added value: +"Route family to filter on (e.g. \"donation\", \"real_estate\", \"business\", \"bonds\")."

addedInput schema / properties / pathway / examples
```
Added value: +[
+  "real_estate"
+]
```

addedInput schema / properties / region / description

Added value: +"Region filter, matched case-insensitively (e.g. \"Caribbean\", \"EU\", \"Middle East\", \"Pacific\", \"Africa\", \"Asia\")."

addedInput schema / properties / region / examples
```
Added value: +[
+  "Caribbean"
+]
```

Changed1 schema field changedJul 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Mirabello response envelope. Tool-specific fields vary; the provenance/disclaimer envelope is always present.",
+  "properties": {
+    "book_a_consultation": {
+      "description": "URL to book a Mirabello consultation.",
+      "type": "string"
+    },
+    "data_updated": {
+      "description": "Date the underlying dataset was last updated.",
+      "type": "string"
+    },
+    "disclaimer": {
+      "description": "Information, not legal/tax/financial/immigration advice; figures indicative.",
+      "type": "string"
+    },
+    "error": {
+      "description": "Present only when the request could not be fulfilled.",
+      "type": "string"
+    },
+    "provider": {
+      "description": "Always \"Mirabello Consultancy\".",
+      "type": "string"
+    },
+    "source": {
+      "description": "Attribution for the data.",
+      "type": "string"
+    },
+    "terms": {
+      "description": "Acceptable-use and information-not-advice terms.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJun 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description adds meaningful behavioral detail: it returns screened countries with key requirements, income thresholds, cost, and path to PR. This tells the agent what kind of output content to expect without relying on schema alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with no filler: the main action is front-loaded, the return contents are summarized, and the important eu-free-movement caveat is placed at the end. Every sentence earns its place.

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 a complete input schema and an output schema present, the description does not need to explain return formats. It covers the purpose, the scope of results, and the key special case, making it sufficiently complete for an agent to call the tool correctly.

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% for both parameters, so the baseline is 3. The description repeats some pathway examples already present in the enum and adds the eu-free-movement definition, but does not add substantial new parameter semantics 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?

The description uses a specific verb and resource: it finds countries offering a given immigration pathway. It names example pathway types and clarifies the special eu-free-movement case, which helps distinguish this pathway-query tool from sibling tools like check_visa_requirement or list_programmes.

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?

The description gives clear context for when to use the tool: when the agent needs to find countries for a particular pathway. It also provides a concrete usage rule about EU/EEA/Swiss citizens using eu-free-movement rather than a visa, though it does not explicitly name or exclude sibling tools.

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.