mcp-server

Generate Personalised Briefing

generate_briefing

Destructive

Generate a personalised Mirabello briefing: given a client profile (nationality, budget, family, goals), returns a ranked shortlist with full family cost math AND a shareable branded briefing page URL (valid 90 days). Optionally registers the client for specialist follow-up (email + consent): that sends a follow-up request to Mirabello. Each call creates a new briefing link, and with email + consent repeating the call sends another request.

Input Schema

TableJSON Schema

Name	Required	Description
`goal`	No	primary goal in own words
`type`	No	citizenship or residency preference (omit for both)
`email`	No	optional — to register for specialist follow-up
`adults`	No	adult applicants incl. spouse (default 1)
`consent`	No	required true if email given (GDPR)
`website`	No	leave blank (spam honeypot)
`tax_goal`	No	True when the applicant's main objective is a tax outcome rather than mobility.
`budget_max`	No	maximum investment budget in USD
`nationality`	No	client nationality (country name)
`programme_ids`	No	optional: specific programmes to brief on (max 3) instead of auto-shortlist
`children_16plus`	No	Number of dependent children aged 16 or over — usually priced higher than under-16s.
`children_under16`	No	Number of dependent children aged under 16 — priced separately by most Caribbean programmes.
`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."

Changed8 schema fields changedSep 23, 2026

addedInput schema / properties / children_16plus / description

Added value: +"Number of dependent children aged 16 or over — usually priced higher than under-16s."

addedInput schema / properties / children_16plus / examples
```
Added value: +[
+  1
+]
```

addedInput schema / properties / children_under16 / description

Added value: +"Number of dependent children aged under 16 — priced separately by most Caribbean programmes."

addedInput schema / properties / children_under16 / examples
```
Added value: +[
+  1
+]
```

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

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

AddedJun 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations set destructiveHint=true and readOnlyHint=false, and the description adds real behavioral value beyond them: it discloses that every call creates a new briefing link, that the URL is valid 90 days, and that repeating the call with email + consent fires another follow-up request (duplicate side effects). It does not explain what the 'destructive' annotation refers to, which keeps it short of 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action and outputs in the first sentence, then uses a second for the optional follow-up and a third for repetition semantics. Dense but efficient; the parenthetical asides are justified rather than filler, though the third sentence is packed.

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, return values need not be spelled out, yet the description still names the key outputs. For a 14-parameter, 0-required tool with full schema coverage and annotations, the main missing piece is guidance on tool selection versus sibling recommenders, everything else an agent needs to call it correctly is present.

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 description coverage is 100%, so the baseline is 3. The description still adds relational meaning the schema does not: it groups nationality/budget/family/goals as the client profile and explicitly ties 'email + consent' together as the follow-up registration trigger, clarifying the GDPR coupling beyond the per-field text.

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 and resource ('Generate a personalised Mirabello briefing') and immediately enumerates the distinctive outputs: a ranked shortlist with family cost math plus a shareable branded briefing page URL. This is clearly separable from sibling list/compare tools like recommend_programmes or compare_programmes.

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

Usage Guidelines3/5

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

The description frames the input context ('given a client profile') and notes the optional follow-up registration path, so usage is implied. However, it never names an alternative tool or states when NOT to use this one (e.g. versus recommend_programmes or compare_programmes), leaving the agent to infer routing.

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.