mcp-server

Create Real-Estate Enquiry

create_enquiry

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). Delivers the enquiry to Mirabello and returns the next step. This is the correct hand-off: CBI/RBI purchases must go through a licensed advisor and a government-approved project — Mirabello manages the property purchase AND the citizenship/residency application end to end.

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

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

Behavior4/5

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

Annotations already indicate this is a side-effecting, non-read-only tool (readOnlyHint=false, openWorldHint=true). The description adds important context beyond that: the enquiry is delivered to an external licensed broker, requires explicit GDPR consent, and returns the next step. There is no contradiction with 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 sentences with no wasted content: the core action is front-loaded, requirements and result are stated compactly, and the final sentence gives the strategic rationale. Every sentence earns its place.

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 a tool with 11 parameters, an output schema, annotations, and many siblings, the description communicates the essential context: what is being routed, to whom, under what consent requirement, and what the caller gets back. It could have more explicitly excluded pure consultation requests, but no critical invocation detail is missing.

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. The description highlights the required trio (property_id, email, consent) and frames consent as GDPR-related, but it largely restates what the schema already conveys. It does not materially enrich individual parameter meaning.

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 clearly states the action ('Route a qualified buyer enquiry about a specific property to Mirabello Consultancy'), identifies the resource (property) and recipient, and separates this tool from read-only siblings like get_property or search_properties. It also specifies the key preconditions in the first sentence.

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?

The description gives strong contextual guidance: it is the correct hand-off for CBI/RBI purchases and explains why Mirabello must be involved. It does not explicitly name alternatives such as book_consultation or get_property, so the when-not-to-use guidance is only implicit rather than fully exclusionary.

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.