Mirabello Immigration Intelligence

Search Properties

search_properties

Read-onlyIdempotent

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 acts as introducer only (it does not sell or broker property); there is no direct developer contact, and all buyer enquiries are routed through Mirabello. Indicative figures; book a consultation to confirm.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_properties"
  }
}

Input 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 to filter listings by: a name in any common spelling ("St Kitts", "Saint Kitts and Nevis", "Greece") or an ISO 3166-1 alpha-2 code ("KN").
`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

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

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / country / description

Previous value: -"Country name to filter listings by (e.g. \"Greece\", \"Portugal\")."New value: +"Country to filter listings by: a name in any common spelling (\"St Kitts\", \"Saint Kitts and Nevis\", \"Greece\") or an ISO 3166-1 alpha-2 code (\"KN\")."

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

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

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses important business behavior: Mirabello acts as introducer only, there is no direct developer contact, all buyer enquiries are routed through Mirabello, figures are indicative, and a consultation is needed to confirm. These are material traits an agent could not infer from annotations or schema.

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 front-loaded with purpose and filters, then moves to return behavior and the introducer disclaimer. It is efficient but the disclaimer sentences are slightly long and overlap, preventing 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?

An output schema exists, and the description still usefully previews what is returned (priced listings, qualifying programme, availability, enquiry route). It is complete enough to call correctly, though it omits any mention of result limiting or pagination—minor since the schema covers limit.

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 coverage is 100%, so the schema already documents all 8 parameters, examples, and enums. The description adds minimal parameter meaning and introduces a slight mismatch in listing_type values ('villa|apartment|residence|plot') versus the schema examples ('apartment, villa, townhouse, land or commercial'). Baseline 3 is appropriate.

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 and resource: 'Search Mirabello-advised investment real estate that QUALIFIES for a citizenship- or residency-by-investment programme.' It clearly separates this from detail-oriented siblings like get_property and from programme-list tools like list_programmes.

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 context for use: only qualifying properties, with the listed filters and business routing through Mirabello. It does not explicitly name alternatives or state when not to use it (e.g., for non-qualifying listings), so it falls short of a 5.

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.