mcp-server

Create Real-Estate Enquiry

create_enquiry

Destructive

Route a qualified buyer enquiry about a specific property to Mirabello Consultancy (the broker of record and licensed advisor). 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.

Input Schema

TableJSON 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

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

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

A3.9/5.0

Behavior4/5

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

Annotations declare this is a non-read-only, destructive write, and the description adds real context beyond them: the side effect of delivering the enquiry to Mirabello, the returned next step, the GDPR consent gate, and the no-duplicate-call warning. It does not explain how an enquiry could later be retracted, so a full 5 is unwarranted.

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?

Four sentences, front-loaded with the purpose and side effect, then preconditions, then the repeat-call rule. Dense but every sentence carries a constraint; borderline between tight and slightly overloaded.

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?

For an 11-parameter mutation with an output schema, the description covers the essentials: recipient, consent gate, side effect, CBI/RBI constraints, and idempotency guidance. Minor gaps remain around what qualifies an enquiry as 'qualified' and how nationality drives eligibility, but the core invocation path is 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 11 parameters, and the baseline is 3. The description reinforces the key required fields (property_id slug format, email, consent:true) but adds no syntax or semantics beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — routing a buyer enquiry about a specific property to Mirabello — and grounds property_id in search_properties/get_property. It clearly differentiates this write/routing action from the read-oriented property siblings, though it does not name a specific alternative tool for related actions.

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?

It gives clear preconditions (property_id slug, valid email, explicit consent:true for GDPR) and an important operational rule ('do not repeat a call that succeeded'). It also scopes CBI/RBI purchases to approved projects and authorised agents, but stops short of explicitly stating when to prefer book_consultation or other siblings instead.

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.