Skip to main content
Glama

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
NameRequiredDescriptionDefault
typeNoProgramme family: "CBI" grants citizenship, "RBI" grants residence (golden visa). Omit for both.
limitNoMaximum number of items to return. Responses can be large; use this to keep the answer small.
countryNoCountry 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_minNoMinimum number of bedrooms.
programmeNoProgramme id whose investment rules the property must satisfy (e.g. "greece-gv").
budget_maxNomax price in USD (best-effort FX)
sale_statusNoAvailability filter, for example available, reserved or sold.
listing_typeNoListing category, for example apartment, villa, townhouse, land or commercial.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent only when the request could not be fulfilled.
termsNoAcceptable-use and information-not-advice terms.
sourceNoAttribution for the data, when it is not Mirabello Consultancy itself.
book_urlNoLink to request a consultation with a Mirabello specialist, for a personal case.
providerNoAlways "Mirabello Consultancy".
disclaimerNoInformation, not legal/tax/financial/immigration advice; figures indicative.
data_updatedNoDate the underlying dataset was last updated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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\")."
  2. Changed3 schema fields changed
    • 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."
  3. Changed14 schema fields changed
    • 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"
      +]
  4. Changed1 schema field changed
    • 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"
      +}
  5. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/destructive=false, so the safety profile is covered. The description adds genuinely new behavioral context: Mirabello is broker of record on every listing, there is no direct developer contact, and all enquiries route through Mirabello, plus a caveat that figures are indicative. It stops short of detailing pagination or response-shape behavior (return format is left to the output 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?

Front-loaded with the search verb and scope, then filters, then returns, then the broker constraint and disclaimer. Dense and mostly every sentence earns its place, though the parenthetical example lists and the closing disclaimer make it longer than strictly needed for selection.

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 an eight-parameter search with a full schema, output schema, and annotations, the description covers scope, filters, return content, and the non-obvious broker-of-record/enquiry-routing constraint. Nothing an agent needs to invoke it correctly appears 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 eight parameters, including the FX caveat and code/spelling flexibility for country. The description mirrors the filter list with example programme ids and a budget_max '(USD, FX-normalised best-effort)' note, but adds little beyond what the schema already states. 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?

States a specific verb (Search) plus resource (Mirabello-advised investment real estate) and narrows the scope to listings that qualify for a citizenship/residency-by-investment programme. An agent can distinguish this from siblings like get_property or list_programmes purely from the description.

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?

Provides clear context for when the tool applies (finding qualifying investment property) and enumerates the filter dimensions an agent should use. It also routes buyers to 'book a consultation to confirm', implicitly pointing at the book_consultation sibling, but it never states exclusions or when a different sibling should be used instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.