mcp-server

Recent Programme Changes

get_recent_changes

Read-only

Recent material changes across investment-migration programmes (launches, closures, threshold/mobility/regulatory changes) + current status counts, PLUS pathway_field_changes (official-source field-level diffs per country x pathway, from->to + cited source) and official_legislation_changes (changes detected directly on official government/gazette sources). The freshest, primary-source-verified record — use for "what changed recently / latest" questions. Pass cc to filter to one country.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cc`	No	ISO 3166-1 alpha-2 country code, uppercase (e.g. "PT" Portugal, "AE" United Arab Emirates, "KN" St Kitts and Nevis).
`limit`	No	Maximum number of items to return. Responses can be large; use this to keep the answer small.

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.

Changed4 schema fields changedSep 23, 2026

addedInput schema / properties / cc / description

Added value: +"ISO 3166-1 alpha-2 country code, uppercase (e.g. \"PT\" Portugal, \"AE\" United Arab Emirates, \"KN\" St Kitts and Nevis)."

addedInput schema / properties / cc / examples
```
Added value: +[
+  "PT",
+  "AE"
+]
```

addedInput schema / properties / limit / description

Added value: +"Maximum number of items to return. Responses can be large; use this to keep the answer small."

addedInput schema / properties / limit / examples
```
Added value: +[
+  10
+]
```

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"
+}

Changed1 schema field changedJun 28, 2026
- addedInput schema / properties / cc
```
Added value: +{
+  "type": "string"
+}
```
AddedJun 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description adds behavioral context beyond annotations: it highlights primary-source verification, freshness, and the structure (field-level diffs from->to + cited source). Annotations already declare readOnlyHint=true, so no contradiction. However, it does not mention pagination or default limits, which is a minor gap.

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?

The description is a single dense paragraph with no wasted words. It front-loads the core purpose, lists specifics, and ends with actionable usage guidance. It is long but justified given the tool's scope.

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?

Given that an output schema exists and annotations cover read-only safety, the description covers all necessary aspects: what data is returned, the source quality, use case, and filtering. Nothing critical is missing for an agent to select and invoke correctly.

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 covers 100% of parameters with descriptive text, but description adds value by explaining that 'cc' filters to a single country and 'limit' keeps the answer small. This reinforces usage intent beyond raw schema definitions, allowing a baseline 3 to be raised.

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 clearly states the tool reports recent changes across investment-migration programmes, and explicitly lists the types of changes covered. It differentiates from siblings by emphasizing primary-source verification and the inclusion of field-level diffs and official legislation changes.

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 explicitly states when to use it ('use for what changed recently / latest questions') and provides a clear filtering instruction. However, it does not mention when not to use it or what alternative to consider (e.g., subscribe_changes for monitoring or get_programme for static details).

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.