mcp-server

Recommend Programmes

recommend_programmes

Read-only

Recommend a ranked shortlist of programmes for a client profile (budget, family size, mobility priority, timeline, tax goal) with reasoning. Respects closed/paused programmes.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	Programme family: "CBI" grants citizenship, "RBI" grants residence (golden visa). Omit for both.
`tax_goal`	No	True when the applicant's main objective is a tax outcome rather than mobility.
`budget_max`	No	Maximum headline minimum investment the applicant will consider, in USD. Programmes with no fixed threshold are excluded from budget filtering.
`family_size`	No	TOTAL number of people to be included, the main applicant INCLUDED (so a couple with two children is 4).
`mobility_priority`	No	True when visa-free travel is the applicant's main objective.
`timeline_max_months`	No	Maximum acceptable time to the outcome, in MONTHS.

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

Changed10 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 / family_size / description

Added value: +"TOTAL number of people to be included, the main applicant INCLUDED (so a couple with two children is 4)."

addedInput schema / properties / family_size / examples
```
Added value: +[
+  4
+]
```

addedInput schema / properties / mobility_priority / description

Added value: +"True when visa-free travel is the applicant's main objective."

addedInput schema / properties / tax_goal / description

Added value: +"True when the applicant's main objective is a tax outcome rather than mobility."

addedInput schema / properties / timeline_max_months / description

Added value: +"Maximum acceptable time to the outcome, in MONTHS."

addedInput schema / properties / timeline_max_months / examples
```
Added value: +[
+  12
+]
```

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

A3.5/5.0

Behavior4/5

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

Annotations already establish that this is a safe, closed-world read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), lowering the burden. The description adds real behavioral context beyond them: recommendations are filtered to respect closed/paused programmes, and the output is ranked with reasoning. It stops short of describing the ranking factors or how ties are broken.

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 action and outcome. The parenthetical parameter list is dense but earns its place by signaling the inputs the agent should gather. No filler.

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-value explanation is not needed, and all six parameters are documented in the schema. The description covers what the tool produces, the profile dimensions it consumes, and the closed/paused filter. It could say more about ranking behavior, but for a read-only recommendation tool this is nearly complete.

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%, so the schema already documents all six optional parameters and even their semantics (e.g., family_size inclusive of applicant, budget_max handling of programmes with no fixed threshold). The description merely restates the dimension names, adding no syntax or interpretation beyond the schema. Baseline 3 applies.

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?

Specific verb ("Recommend") plus resource ("programmes") and a clearly bounded output ("ranked shortlist ... with reasoning"). It implicitly separates itself from list_programmes (raw list) and compare_programmes (comparison), but never names those siblings to make the distinction explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance. It does not tell the agent how this differs from compare_programmes, find_fastest_citizenship, find_low_tax, or plan_path, all of which overlap on the same recommendation space. Usage is only inferable from the listed profile dimensions.

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.