Mirabello Immigration Intelligence

Create Real-Estate Enquiry

create_enquiry

Destructive

Route a qualified buyer enquiry about a specific property to Mirabello Consultancy, which acts as introducer only (it does not sell or broker property). Requires property_id (slug) + a valid email + explicit consent:true (GDPR). Side effect: delivers the enquiry to Mirabello and returns the next step. CBI/RBI property purchases must use a government-approved project and an authorised agent; Mirabello handles the purchase and the citizenship/residency application. Each call sends a separate enquiry, so do not repeat a call that succeeded.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "property_id": "<property_id>",
      "email": "<email>",
      "consent": "<consent>"
    },
    "name": "create_enquiry"
  }
}

Input Schema

Name	Required	Description
`name`	No	Enquirer full name, only as the user has given it. Never invent or infer personal details.
`email`	Yes	Contact email address for the enquiry. Only ever send an address the user has explicitly provided for this purpose.
`phone`	No	Contact telephone number in international format, only if the user has provided it.
`budget`	No	Budget the enquirer has stated, in their own words including the currency.
`consent`	Yes	must be true (GDPR consent to share details with Mirabello)
`message`	No	The enquiry itself in the user’s own words. Do not add commitments or figures the user did not state.
`timeline`	No	When the enquirer wants to proceed, in their own words (e.g. "within 3 months").
`nationality`	No	Applicant's current citizenship, as a country name (for example India, Nigeria, Russia). Drives eligibility restrictions.
`property_id`	Yes	listing slug from search_properties/get_property
`preferred_channel`	No	How the enquirer prefers to be contacted: email, phone or WhatsApp.
`residence_country`	No	Country where the enquirer currently lives.

Output Schema

Name	Required	Description	Default
`error`	No
`terms`	No
`source`	No
`book_url`	No
`provider`	No
`disclaimer`	No
`data_updated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 25, 2026

changedOutput schema / description

Previous value: -"Mirabello response envelope. Tool-specific fields vary; the provenance/disclaimer envelope is always present."New value: +"Mirabello envelope; tool fields vary; error only on failure."

removedOutput schema / properties / book_url / description

Removed value: -"Link to request a consultation with a Mirabello specialist, for a personal case."

removedOutput schema / properties / data_updated / description

Removed value: -"Date the underlying dataset was last updated."

removedOutput schema / properties / disclaimer / description

Removed value: -"Information, not legal/tax/financial/immigration advice; figures indicative."

removedOutput schema / properties / error / description

Removed value: -"Present only when the request could not be fulfilled."

removedOutput schema / properties / provider / description
```
Removed value: -"Always \"Mirabello Consultancy\"."
```

removedOutput schema / properties / source / description

Removed value: -"Attribution for the data, when it is not Mirabello Consultancy itself."

removedOutput schema / properties / terms / description

Removed value: -"Acceptable-use and information-not-advice terms."

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

Changed11 schema fields changedSep 23, 2026

addedInput schema / properties / budget / description

Added value: +"Budget the enquirer has stated, in their own words including the currency."

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

addedInput schema / properties / message / description

Added value: +"The enquiry itself in the user’s own words. Do not add commitments or figures the user did not state."

addedInput schema / properties / name / description

Added value: +"Enquirer full name, only as the user has given it. Never invent or infer personal details."

addedInput schema / properties / nationality / description

Added value: +"Applicant's current citizenship, as a country name (for example India, Nigeria, Russia). Drives eligibility restrictions."

addedInput schema / properties / nationality / examples
```
Added value: +[
+  "India"
+]
```

addedInput schema / properties / phone / description

Added value: +"Contact telephone number in international format, only if the user has provided it."

addedInput schema / properties / preferred_channel / description

Added value: +"How the enquirer prefers to be contacted: email, phone or WhatsApp."

addedInput schema / properties / preferred_channel / examples
```
Added value: +[
+  "email"
+]
```
addedInput schema / properties / residence_country / description
```
Added value: +"Country where the enquirer currently lives."
```

addedInput schema / properties / timeline / description

Added value: +"When the enquirer wants to proceed, in their own words (e.g. \"within 3 months\")."

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 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=false; the description explains why — the enquiry is delivered irrevocably to a third party and each call sends a separate enquiry, so retries duplicate. It also discloses the GDPR consent gate and that eligibility varies for CBI/RBI routes. Remaining minor gap: no mention of failure/partial-delivery handling.

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?

The core action, requirements and side effect are front-loaded in the first three sentences with no filler. The closing CBI/RBI sentence is the weakest link — useful eligibility context but tangential to how the tool is invoked — so not a 5.

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 no explanation, and the description covers the side effect, non-idempotence, consent, and the introducer role. For an 11-parameter mutation tool this is close to complete; only edge-case behavior (duplicate-submission handling, error cases) is unaddressed.

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 11 fields including the 'never invent personal details' constraints. The description adds only the required-field set and the GDPR meaning of consent, which is reinforcement rather than new semantics. Baseline 3 applies.

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+resource ('Route a qualified buyer enquiry about a specific property to Mirabello') and immediately scopes the relationship (introducer only, does not sell or broker). It is clearly distinct from the listing-discovery siblings search_properties and get_property, which it references as the source of property_id.

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?

Gives explicit preconditions (property_id slug, valid email, consent:true) and points to search_properties/get_property for obtaining the slug, plus an anti-pattern warning ('do not repeat a call that succeeded'). It does not explicitly contrast with sibling book_consultation, so it stops short of full when/when-not routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mirabello Immigration Intelligence 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.