mcp-server

List Programmes

list_programmes

Read-only

List Mirabello-advised citizenship- (CBI) and residency-by-investment (RBI/golden visa) programmes, optionally filtered by type, budget (USD, compared at indicative FX), region, or max processing time. All 98 programmes is a large response — pass limit when you only need a sample. Budget filters exclude programmes with no fixed threshold, which are still listed unfiltered.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	Programme family: "CBI" grants citizenship, "RBI" grants residence (golden visa). Omit for both.
`limit`	No	Maximum number of items to return. Responses can be large; use this to keep the answer small.
`region`	No	Region filter, matched case-insensitively (e.g. "Caribbean", "EU", "Middle East", "Pacific", "Africa", "Asia").
`budget_max`	No	Maximum headline minimum investment the applicant will consider, in USD. Programmes with no fixed threshold are excluded from budget filtering.
`max_processing_months`	No	Maximum acceptable processing time in MONTHS, compared against the lower bound of each programme's published range.

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

Changed9 schema fields changedSep 23, 2026

addedInput schema / properties / budget_max / description

Added value: +"Maximum headline minimum investment the applicant will consider, in USD. Programmes with no fixed threshold are excluded from budget filtering."

addedInput schema / properties / budget_max / examples
```
Added value: +[
+  250000
+]
```

addedInput schema / properties / limit

Added value: +{
+  "description": "Maximum number of items to return. Responses can be large; use this to keep the answer small.",
+  "examples": [
+    10
+  ],
+  "type": "number"
+}

addedInput schema / properties / max_processing_months / description

Added value: +"Maximum acceptable processing time in MONTHS, compared against the lower bound of each programme's published range."

addedInput schema / properties / max_processing_months / examples
```
Added value: +[
+  6
+]
```

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"
+]
```

addedInput schema / properties / type / description

Added value: +"Programme family: \"CBI\" grants citizenship, \"RBI\" grants residence (golden visa). Omit for both."

addedInput schema / properties / type / examples
```
Added value: +[
+  "CBI"
+]
```

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

First observedJun 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world). The description adds genuinely useful behaviour beyond that: the corpus is ~98 items and large, and budget filtering silently excludes programmes with no fixed threshold while still listing them unfiltered. It omits pagination behaviour beyond limit, keeping it from a 5.

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?

Three sentences, all front-loaded with the resource and its filters first, then scale caveat, then the filter-exclusion edge case. No filler and every clause conveys actionable information.

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 and annotations covering safety, the description only needs to explain filtering semantics and response scale, which it does. The remaining gap is routing context: no mention of when compare_programmes or recommend_programmes should be preferred over this listing 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 each parameter already documents its own semantics, so the baseline is 3. The description adds one real nuance — budget comparison occurs at indicative FX — but the exclusion rule and CBI/RBI definitions merely restate 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 (List) and resource (Mirabello-advised CBI/RBI programmes) with scope qualifiers, and distinguishes itself from get_programme (single) and compare_programmes (comparison) by framing itself as a filtered enumeration. An agent can identify the correct tool 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?

Gives conditional guidance: pass limit for a sample, and how budget filters interact with programmes lacking a fixed threshold. It does not explicitly route the agent away from siblings such as recommend_programmes or compare_programmes when those are more appropriate, so it falls short of a full 5.

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.