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

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.1/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=false). The description adds meaningful behavioral context beyond that: results are 'screened' countries, each returned with key requirements, income thresholds, cost and path to PR, which tells the agent what a successful call yields and that the dataset is curated.

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?

Three sentences, front-loaded with the primary action and scope, and the EU/EEA caveat placed last where it belongs. Some waste in restating enum values that the schema already carries, but the density is otherwise high.

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 needn't enumerate return fields, yet it summarizes the shape usefully and resolves the one genuinely ambiguous enum value. It omits any mention of the region filter or how screening is performed, leaving a small gap for a two-parameter discovery tool.

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% and the schema already enumerates all pathway ids plus a description of eu-free-movement, so the description's example list (digital-nomad, skilled-work, ancestry-descent, retirement-passive) largely duplicates structured data. The region parameter is never addressed, and no format or matching semantics are added beyond what the schema states.

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 ('Find which countries offer a given immigration pathway') and immediately constrains the domain by listing the pathway types it operates on. An agent can distinguish it from siblings such as find_retirement_routes (route discovery) or check_eligibility (per-user assessment) without opening the schema.

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 routing rule: EU/EEA/Swiss citizens moving within the EU/EEA or Switzerland should use eu-free-movement rather than a visa pathway. It does not, however, say when to use this tool instead of close siblings like find_retirement_routes or check_eligibility, so the guidance is clear but incomplete.

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.