mcp-server

Search Properties

search_properties

Read-only

Search Mirabello-advised investment real estate that QUALIFIES for a citizenship- or residency-by-investment programme. Filter by country, programme (e.g. "grenada-citizenship-by-investment", "greece-golden-visa"), type (CBI|RBI), budget_max (USD, FX-normalised best-effort), beds_min, listing_type (villa|apartment|residence|plot), sale_status. Returns priced listings with the qualifying programme, availability, and the Mirabello enquiry route. Mirabello Consultancy is broker of record on every listing — there is no direct developer contact; all buyer enquiries are routed through Mirabello. Indicative figures; book a consultation to confirm.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	Programme family: "CBI" grants citizenship, "RBI" grants residence (golden visa). Omit for both.
`limit`	No	Maximum number of items to return. Responses can be large; use this to keep the answer small.
`country`	No	Country name to filter listings by (e.g. "Greece", "Portugal").
`beds_min`	No	Minimum number of bedrooms.
`programme`	No	Programme id whose investment rules the property must satisfy (e.g. "greece-gv").
`budget_max`	No	max price in USD (best-effort FX)
`sale_status`	No	Availability filter, for example available, reserved or sold.
`listing_type`	No	Listing category, for example apartment, villa, townhouse, land or commercial.

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.

Changed14 schema fields changedSep 23, 2026

addedInput schema / properties / beds_min / description
```
Added value: +"Minimum number of bedrooms."
```
addedInput schema / properties / beds_min / examples
```
Added value: +[
+  2
+]
```

addedInput schema / properties / country / description

Added value: +"Country name to filter listings by (e.g. \"Greece\", \"Portugal\")."

addedInput schema / properties / country / examples
```
Added value: +[
+  "Greece"
+]
```

addedInput schema / properties / limit / description

Added value: +"Maximum number of items to return. Responses can be large; use this to keep the answer small."

addedInput schema / properties / limit / examples
```
Added value: +[
+  10
+]
```

addedInput schema / properties / listing_type / description

Added value: +"Listing category, for example apartment, villa, townhouse, land or commercial."

addedInput schema / properties / listing_type / examples
```
Added value: +[
+  "apartment"
+]
```

addedInput schema / properties / programme / description

Added value: +"Programme id whose investment rules the property must satisfy (e.g. \"greece-gv\")."

addedInput schema / properties / programme / examples
```
Added value: +[
+  "greece-gv"
+]
```

addedInput schema / properties / sale_status / description

Added value: +"Availability filter, for example available, reserved or sold."

addedInput schema / properties / sale_status / examples
```
Added value: +[
+  "available"
+]
```

addedInput schema / properties / type / description

Added value: +"Programme family: \"CBI\" grants citizenship, \"RBI\" grants residence (golden visa). Omit for both."

addedInput schema / properties / type / examples
```
Added value: +[
+  "CBI"
+]
```

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 already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond that: it discloses the broker-of-record arrangement (no direct developer contact, all enquiries routed through Mirabello), the indicative nature of figures, and the FX-normalisation caveat for budget_max. These details set expectations about data accuracy and the enquiry flow without contradicting annotations.

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 description is structured with a clear lead sentence, a filter list, a returns statement, and then two caveats. It is slightly verbose—the broker-of-record and indicative-figures sentences could be trimmed—but every sentence contributes either to scope, filters, or expectations. No fluff; it earns a 4 for being informative yet reasonably compact.

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?

Given the 8 parameters and existing output schema, the description covers the essential aspects: what is searched, available filters, return content, and two important caveats (broker route, indicative figures). It does not describe default ordering, pagination, or the behavior of the 'limit' parameter, but those are likely covered by the schema or are minor. Overall, the description is sufficiently complete for an agent to call the tool correctly.

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 input schema already documents every parameter with descriptions and examples. The description repeats some of these (type, programme, budget_max, etc.) but adds little beyond the schema. The only marginal addition is the clarification that budget_max is 'USD, FX-normalised best-effort,' which is already in the schema ('max price in USD (best-effort FX)'). Since the schema carries the full burden, this is a baseline 3.

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 opens with a specific verb ('Search') and a clearly bounded resource ('Mirabello-advised investment real estate that QUALIFIES for a citizenship- or residency-by-investment programme'). It explicitly differentiates from siblings like get_property (specific property lookup) and list_programmes (programme catalog) by focusing on qualifying listings. The filter list and return content make the tool's role unambiguous.

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 explains the tool's purpose and what it returns, making it clear when to use it: when the agent needs to find qualifying real estate. However, it does not explicitly state when NOT to use it or name alternatives (e.g., 'use get_property for a specific listing' or 'use check_eligibility for personal eligibility'). The context is implied but not stated as exclusions, so it earns a 4 rather than a 5.

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.