mcp-server

Generate Personalised Briefing

generate_briefing

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

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

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/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, and the description adds complementary behavioral context: the generated URL expires after 90 days, and the tool can register the client for specialist follow-up contingent on email and consent (GDPR). These are genuine side-effect disclosures beyond the annotation flags. Minor gaps remain (e.g., what data is stored on registration, whether an email is dispatched), but nothing contradicts the annotations.

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 and roughly 50 words with the core function and inputs front-loaded in the first sentence and the optional side effect in the second. Every clause carries information and nothing repeats schema or annotation content.

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?

Given an output schema, safety annotations, and 100% parameter coverage, the description only needs to carry behavioral and selection essentials, which it does: inputs, outputs, URL validity, and optional registration. The notable gap is that all 14 parameters are optional and the description never states which combination yields a valid briefing. The absence of sibling-differentiation guidance also keeps this from a 5.

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 baseline is 3 even without parameter detail in the description. The description adds modest value by grouping parameters into a 'client profile' and hinting that family composition drives the cost math (children under/over 16 are priced separately in the schema). It does not, however, explain any parameter beyond what the schema already documents.

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 opens with a specific verb+resource ('Generate a personalised Mirabello briefing') and enumerates distinct outputs — a ranked shortlist, full family cost math, and a branded shareable URL valid 90 days — that clearly separate it from siblings like recommend_programmes or estimate_total_cost. Inputs (nationality, budget, family, goals) are named, so an agent understands both function and scope 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 Guidelines3/5

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

Usage context is implied by the listed inputs (a client profile with nationality, budget, family, goals), and the prerequisite for the optional registration (email + consent) is stated. However, in a sibling set of 60+ tools, no exclusions or alternatives are named — an agent is not told to prefer estimate_total_cost or recommend_programmes for narrower requests. This leaves the when-not-to-use decision to inference.

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.