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

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

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context by specifying what the returned profile includes: requirements, cost, processing, rights, path to PR/citizenship, and the official source, and by emphasizing exhaustiveness ('ALL screened pathways'). No contradiction with annotations.

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?

Two sentences with no filler: the core resource and scope are front-loaded, the parameter format is given with concrete examples, and every clause adds information.

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 read-only lookup with one required parameter, a rich output schema, and full schema parameter descriptions, the description provides everything an agent needs to select and invoke the tool. Nothing material is missing.

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% and the schema already documents the cc, pathway, and nationality parameters, including the free-movement special case. The description only reinforces the ISO alpha-2 format, adding no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource ('Country immigration profile') and scope ('ALL screened pathways'), enumerating pathway types and explicitly noting 'beyond investment migration'. This distinguishes it from investment-migration siblings, though it lacks an explicit verb like 'get' or 'retrieve' and does not name alternative tools.

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?

It defines when the tool applies: all screened immigration pathways beyond investment migration, and it instructs the caller to use an ISO-3166 alpha-2 code. However, it does not explicitly state when to prefer this over sibling tools such as get_programme, list_programmes, or find_pathways, leaving routing largely implied.

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.