mcp-server

Get Property

get_property

Read-only

Full detail for one investment property by slug: price, specs, location, qualifying programme + holding period, project/developer (where disclosed), availability and freshness. Mirabello Consultancy is broker of record; brochure, floor plan and due-diligence pack are available from Mirabello on enquiry. Indicative; verify with Mirabello.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Listing slug exactly as returned by search_properties.

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 / slug / description
```
Added value: +"Listing slug exactly as returned by search_properties."
```

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

Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint, so the read-only safety profile is covered. The description adds valuable context beyond annotations: data is 'indicative' and must be verified with Mirabello, and documents such as brochure and due-diligence pack are not returned by the tool but must be requested separately.

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 with no filler: the first front-loads the core purpose and content fields, and the second adds the broker-of-record and verification caveat. Every clause contributes meaningful information for invoking the tool correctly.

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

Completeness5/5

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

For a read-only single-parameter lookup with a full output schema, this description is complete. It covers what data is included, acknowledges missing-data cases ('where disclosed'), and warns that values are indicative and require verification with the broker.

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% and the single required parameter slug is already well documented in the schema. The description only repeats that lookup is by slug and adds no new meaning or constraints 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 and resource: 'Full detail for one investment property by slug', and enumerates the exact data domains returned (price, specs, location, programme, developer, availability, freshness). This clearly distinguishes it from sibling get_* tools like get_property_law or get_programme, and from search_properties which returns listings rather than one property.

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 slug parameter is defined as 'exactly as returned by search_properties', which strongly implies the tool is meant to be used after a search to retrieve full detail for a chosen listing. There is no explicit mention of alternatives or exclusions, but the 'one investment property by slug' scoping gives clear usage 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.