mcp-server

Country Intelligence

get_country

Read-only

Country immigration profile (beyond investment migration): ALL screened pathways for a country — skilled-work, digital-nomad, retirement, citizenship-by-descent, naturalisation, study, family etc. — each with requirements, cost, processing, rights, path to PR/citizenship and the official source. Use the ISO-3166 alpha-2 code (e.g. CA, GB, DE, PT).

Input Schema

TableJSON Schema

Name	Required	Description
`cc`	Yes	ISO alpha-2 country code
`pathway`	No	optional: one pathway id to return
`nationality`	No	optional: the applicant's citizenship (ISO alpha-2 or name). For an EU/EEA/Swiss citizen in an EU/EEA country or Switzerland, free movement is shown as their route, national visas are marked not needed and golden visas are omitted.

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 / nationality

Added value: +{
+  "description": "optional: the applicant's citizenship (ISO alpha-2 or name). For an EU/EEA/Swiss citizen in an EU/EEA country or Switzerland, free movement is shown as their route, national visas are marked not needed and golden visas are omitted.",
+  "type": "string"
+}

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

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds useful scope context — this is a registry-style lookup returning screened pathways with official sources rather than advice — but discloses no rate limits, coverage caveats, or behaviour when a country has no pathways. Adds some value, not rich behavioural detail.

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?

Two sentences, front-loaded with the resource and scope, then the calling convention. The mid-sentence em-dash catalogue of pathways is dense but it is the substantive payload; nothing reads as filler.

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?

An output schema exists, so return values need no further explanation, and the description already characterises the shape of the payload (per-pathway requirements, cost, processing, rights, official source). For a 3-parameter read-only lookup this is complete enough to invoke 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%, so the schema already documents cc, pathway and nationality, including the detailed EU/EEA free-movement behaviour for nationality. The description only reinforces cc format with examples (CA, GB, DE, PT). With the schema doing the heavy lifting, 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 states a concrete resource ('country immigration profile') and enumerates exactly what it returns: every screened pathway — skilled-work, digital-nomad, retirement, citizenship-by-descent, naturalisation, study, family — each with requirements, cost, processing, rights, and PR/citizenship path. The parenthetical '(beyond investment migration)' and 'ALL screened pathways' implicitly separate it from get_programme and find_pathways, so the agent can discriminate without opening schemas.

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?

Usage is only implied: the tool is framed as broader than investment migration, and the ISO alpha-2 calling convention is given, but no sibling is named as the alternative and there is no explicit when-not-to-use guidance (e.g. use get_programme for a single investment programme, or find_pathways to search across countries). Adequate but leaves the routing decision to inference.

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.