mcp-server

Compare Programmes

compare_programmes

Read-only

Compare programmes side by side. Pass a + b (two programme ids) for the canonical versioned comparison artefact from the Mirabello Investment Migration Index: rank, composite, the dimension scores, per-dimension deltas, per-metric leads (a|b|tie) and the human compare page URL where one exists. Or pass ids (2-4) for the classic multi-column comparison of cost, processing, mobility, family inclusion, tax, path to citizenship.

Input Schema

TableJSON Schema

Name	Required	Description
`a`	No	programme id (use with b) for the canonical two-programme artefact
`b`	No	programme id (use with a)
`ids`	No	2-4 programme ids for the classic comparison

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

Changed4 schema fields changedJul 3, 2026

addedInput schema / properties / a

Added value: +{
+  "description": "programme id (use with b) for the canonical two-programme artefact",
+  "type": "string"
+}

addedInput schema / properties / b

Added value: +{
+  "description": "programme id (use with a)",
+  "type": "string"
+}

addedInput schema / properties / ids / description

Added value: +"2-4 programme ids for the classic comparison"

removedInput schema / required
```
Removed value: -[
-  "ids"
-]
```

First observedJun 4, 2026

TDQS

A4.3/5.0

Behavior4/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. The description goes beyond them by disclosing the returned artefacts (rank, composite, dimension scores, per-dimension deltas, per-metric leads, compare page URL) and qualifying the URL with 'where one exists', which signals the field can be absent.

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 core purpose, and the alternative mode is presented as an explicit 'Or'. The comma-separated output lists are somewhat dense but each item earns its place by describing a distinct result field.

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?

An output schema exists, so return values need not be fully re-explained, and the safety annotations cover the rest. Both invocation modes and their differing artefacts are described, leaving only minor gaps such as which mode takes precedence if both are supplied.

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 coverage is 100%, so the baseline would be 3, but the description adds genuine semantics: it maps the parameter choice to the type of result (a+b yields the versioned artefact; ids yields the classic column set). It does not explain the a-vs-b ordering or ID format, but the mode-mapping is real value 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?

States a specific verb+resource ('Compare programmes side by side') and then distinguishes two distinct operating modes: the pair (a+b) canonical versioned artefact versus the ids multi-column classic comparison. An agent can tell exactly what output shape each invocation produces.

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?

Gives explicit conditional guidance: 'Pass a + b ... for the canonical versioned comparison artefact' and 'Or pass ids (2-4) for the classic multi-column comparison'. It does not, however, differentiate itself from siblings with similar names (compare_formation, compare_scenarios, compare_treaty_position), leaving the agent to infer that this tool is the programme-specific one.

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.