mcp-server

Book Consultation

book_consultation

Book a free consultation with Mirabello Consultancy. Requires email + programme interest/message and explicit consent. Delivers the enquiry to Mirabello and returns a tracked booking URL.

Input Schema

TableJSON Schema

Name	Required	Description
`goal`	No	why / use-case (e.g. second passport, EU residency, tax, mobility, family relocation)
`name`	No	full name
`email`	Yes	Contact email address for the enquiry. Only ever send an address the user has explicitly provided for this purpose.
`phone`	No	phone / WhatsApp (with country code)
`budget`	No	investment budget or band (e.g. "$250k", "up to $500k")
`source`	No	origin surface of this lead for attribution, e.g. "plan_path" when booking follows a plan_path result
`consent`	No	User consents to share details with Mirabello Consultancy (GDPR). Must be true to deliver.
`message`	No	short comment / interest description
`website`	No	leave blank (spam honeypot)
`timeline`	No	desired timeline (e.g. "ASAP", "6 months", "within a year")
`lead_heat`	No	optional pre-assessed lead heat (e.g. carry the plan_path conversion.lead_heat through) — escalates routing for qualified HNWIs
`salutation`	No	salutation / honorific
`family_size`	No	who is included (e.g. "single", "couple", "family of 4") — optional summary; prefer number_of_children + childrens_ages
`nationality`	No	current nationality (country name)
`childrens_ages`	No	children ages, comma-separated (e.g. 5, 12, 17)
`marital_status`	No	married? Yes/No
`preferred_channel`	No	how the client prefers to be contacted
`residence_country`	No	current country of residence (if different from nationality)
`number_of_children`	No	how many children to include
`programme_interest`	No	programme or shortlist of interest (e.g. "st-kitts-cbi" or "CBI Caribbean", or service category: "Citizenship by Investment", "Residency by Investment", "Citizenship by Marriage", "Citizenship by Descent", "Passport Renewal", "Government Advisory")

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.

Changed1 schema field changedSep 23, 2026

addedInput schema / properties / email / description

Added value: +"Contact email address for the enquiry. Only ever send an address the user has explicitly provided for this purpose."

Changed2 schema fields changedJul 30, 2026

removedInput schema / properties / conversation_summary

Removed value: -{
-  "description": "a short specialist-ready qualification summary of the chat so far (what the person wants, key facts they shared, budget/timeline/nationality signals, objections, open questions). The Mira layer injects this automatically; not for LLM-invented content.",
-  "type": "string"
-}

removedInput schema / properties / transcript

Removed value: -{
-  "description": "the full user↔Mira conversation transcript for the specialist to review. Injected automatically by the Mira layer.",
-  "type": "string"
-}

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

Changed2 schema fields changedJul 5, 2026

addedInput schema / properties / conversation_summary

Added value: +{
+  "description": "a short specialist-ready qualification summary of the chat so far (what the person wants, key facts they shared, budget/timeline/nationality signals, objections, open questions). The Mira layer injects this automatically; not for LLM-invented content.",
+  "type": "string"
+}

addedInput schema / properties / transcript

Added value: +{
+  "description": "the full user↔Mira conversation transcript for the specialist to review. Injected automatically by the Mira layer.",
+  "type": "string"
+}

Changed2 schema fields changedJun 28, 2026

addedInput schema / properties / lead_heat

Added value: +{
+  "description": "optional pre-assessed lead heat (e.g. carry the plan_path conversion.lead_heat through) — escalates routing for qualified HNWIs",
+  "enum": [
+    "hot",
+    "warm",
+    "info"
+  ],
+  "type": "string"
+}

addedInput schema / properties / source

Added value: +{
+  "description": "origin surface of this lead for attribution, e.g. \"plan_path\" when booking follows a plan_path result",
+  "type": "string"
+}

Changed10 schema fields changedJun 6, 2026

addedInput schema / properties / childrens_ages

Added value: +{
+  "description": "children ages, comma-separated (e.g. 5, 12, 17)",
+  "type": "string"
+}

changedInput schema / properties / family_size / description

Previous value: -"who is included (e.g. \"single\", \"couple\", \"family of 4\")"New value: +"who is included (e.g. \"single\", \"couple\", \"family of 4\") — optional summary; prefer number_of_children + childrens_ages"

addedInput schema / properties / marital_status

Added value: +{
+  "description": "married? Yes/No",
+  "enum": [
+    "Yes",
+    "No"
+  ],
+  "type": "string"
+}

addedInput schema / properties / message / description

Added value: +"short comment / interest description"

addedInput schema / properties / name / description
```
Added value: +"full name"
```

changedInput schema / properties / nationality / description

Previous value: -"current nationality / country of residence"New value: +"current nationality (country name)"

addedInput schema / properties / number_of_children

Added value: +{
+  "description": "how many children to include",
+  "type": "number"
+}

changedInput schema / properties / programme_interest / description

Previous value: -"programme or shortlist of interest (e.g. \"st-kitts-cbi\" or \"CBI Caribbean\")"New value: +"programme or shortlist of interest (e.g. \"st-kitts-cbi\" or \"CBI Caribbean\", or service category: \"Citizenship by Investment\", \"Residency by Investment\", \"Citizenship by Marriage\", \"Citizenship by Descent\", \"Passport Renewal\", \"Government Advisory\")"

addedInput schema / properties / residence_country

Added value: +{
+  "description": "current country of residence (if different from nationality)",
+  "type": "string"
+}

addedInput schema / properties / salutation

Added value: +{
+  "description": "salutation / honorific",
+  "enum": [
+    "Mr.",
+    "Ms.",
+    "Mrs.",
+    "Sheikh",
+    "Prof.",
+    "Dr."
+  ],
+  "type": "string"
+}

Changed8 schema fields changedJun 5, 2026

addedInput schema / properties / budget

Added value: +{
+  "description": "investment budget or band (e.g. \"$250k\", \"up to $500k\")",
+  "type": "string"
+}

addedInput schema / properties / family_size

Added value: +{
+  "description": "who is included (e.g. \"single\", \"couple\", \"family of 4\")",
+  "type": "string"
+}

addedInput schema / properties / goal

Added value: +{
+  "description": "why / use-case (e.g. second passport, EU residency, tax, mobility, family relocation)",
+  "type": "string"
+}

addedInput schema / properties / nationality

Added value: +{
+  "description": "current nationality / country of residence",
+  "type": "string"
+}

addedInput schema / properties / phone

Added value: +{
+  "description": "phone / WhatsApp (with country code)",
+  "type": "string"
+}

addedInput schema / properties / preferred_channel

Added value: +{
+  "description": "how the client prefers to be contacted",
+  "enum": [
+    "email",
+    "phone",
+    "whatsapp",
+    "telegram",
+    "wechat"
+  ],
+  "type": "string"
+}

addedInput schema / properties / programme_interest / description

Added value: +"programme or shortlist of interest (e.g. \"st-kitts-cbi\" or \"CBI Caribbean\")"

addedInput schema / properties / timeline

Added value: +{
+  "description": "desired timeline (e.g. \"ASAP\", \"6 months\", \"within a year\")",
+  "type": "string"
+}

First observedJun 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already indicate a write operation (readOnlyHint=false) and non-destructive nature. The description adds that the enquiry is delivered to Mirabello (external data sharing) and requires explicit consent, plus it returns a tracked booking URL. These are meaningful behavioral traits beyond 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?

Three short sentences with zero redundancy. The core action is front-loaded, and the requirements and outcome are stated efficiently. No fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (20 parameters) and the presence of a detailed output schema, the description is adequate but not exhaustive. It does not guide the agent on which optional parameters matter most or provide any edge-case handling, but the schema's rich descriptions largely compensate. It could be more helpful for a tool this complex.

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 all 20 parameters are already documented in detail. The description adds that email, programme interest/message, and consent are required together, which is not explicit in the schema (only email is required). This is a useful but minor addition beyond 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 ('Book') and resource ('free consultation with Mirabello Consultancy'), and adds key requirements and output. It clearly distinguishes itself from sibling tools like create_enquiry by focusing on booking a consultation rather than a generic enquiry.

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?

The description lists prerequisites (email, programme interest/message, consent) but gives no guidance on when to use this tool vs alternatives such as create_enquiry or plan_path. No exclusions or alternative routing are mentioned, leaving the agent to infer the appropriate context.

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.