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

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

A4.2/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, so the safety profile is covered. The description adds meaningful behavioral context: it respects closed/paused programmes, meaning the tool filters out unavailable options. It also implies the output includes reasoning, which is a behavioral trait beyond a simple list. It doesn't mention pagination or output size, but the output schema likely covers that.

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 zero waste. The first sentence states the core function and inputs; the second adds a critical filtering behavior. Front-loaded and efficient.

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?

The tool has an output schema, so return values are documented elsewhere. The description covers the input context, the ranking behavior, and the closed/paused filter. It doesn't explicitly state what 'reasoning' looks like or how many programmes are returned, but the output schema likely covers that. For a recommendation tool with rich schema and annotations, 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 description coverage is 100%, so the schema already documents all 6 parameters thoroughly. The description adds a high-level summary of the input criteria but doesn't add new meaning beyond the schema. Baseline 3 is appropriate because the schema does the heavy lifting.

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 states a specific verb ('Recommend'), a resource ('a ranked shortlist of programmes'), and the input context ('client profile') with explicit criteria. It also distinguishes itself from siblings like compare_programmes and list_programmes by emphasizing ranking and reasoning for a client profile.

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 implies when to use this tool: when a client profile with budget, family size, mobility priority, timeline, and tax goal is provided. It doesn't explicitly name alternatives or exclusions, but the context signals and sibling names (e.g., compare_programmes, list_programmes) make the use case clear. It could be improved by explicitly saying 'use compare_programmes for side-by-side comparison' or 'use list_programmes for unfiltered lists'.

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.