Skip to main content
Glama

Cubi Estate

Find similar homes nearby

find_similar_homes
Read-only

Homes like one listing in its own market, picked by Cubi's similarity model.

Use when the user likes a home and wants more like it nearby ("more like
#2", "anything similar?"). Returns up to `limit` listings in the same city
with the same type family and a similar size, ranked by Cubi's similarity
model: a nearest-neighbour search over each listing's concept embedding (a
50-dimension PCA of its catalogued features) followed by a hybrid ranker
over stated features, size, location and asking price; `method` says
which embedding served the request. Each match carries a `card` (price,
size, place, link) and a `why` sentence written by the ranker from what
both listings state ("same city · within 7% on price") — relay that
reason, don't invent one. Asking prices, not valuations: never call a
match cheaper "better value".

For a home like this one in ANOTHER city, call `find_similar_elsewhere`.

Args:
    listing_id: Source-prefixed id of a listing already shown (e.g.
        `remax:12345`). Do not invent one.
    lang: ISO 639-1 code (en/pt/es/fr/de/nl/ru) for the `why` sentences.
    limit: How many matches to return (1-5, default 3).

Returns:
    JSON: seed_id, count, method {embedding, ranker, scope}, matches[{card,
    why, similarity}]; or a not-found message.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listing_id": "<listing_id>"
    },
    "name": "find_similar_homes"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoISO 639-1 code (en/pt/es/fr/de/nl/ru) for the `why` sentences.en
limitNoHow many matches to return (1-5, default 3).
listing_idYesSource-prefixed id of a listing already shown (e.g. `remax:12345`). Do not invent one.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / lang / description
      Added value: +"ISO 639-1 code (en/pt/es/fr/de/nl/ru) for the `why` sentences."
    • addedInput schema / properties / limit / description
      Added value: +"How many matches to return (1-5, default 3)."
    • addedInput schema / properties / listing_id / description
      Added value: +"Source-prefixed id of a listing already shown (e.g. `remax:12345`). Do not invent one."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuinely new behavioral context: the ranking pipeline, the `method` provenance field, and what to do with the `why` reason. It also issues an interpretive guardrail ('relay that reason, don't invent one') and a semantic caution ('asking prices, not valuations — never call a match cheaper better value').

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 purpose and trigger, then behavior, then the sibling pointer, then args. Mostly efficient, but the internal detail (50-dimension PCA embedding, hybrid ranker) is heavier than an agent needs to select or call the tool.

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 3-parameter read tool with full schema coverage and an output schema, the description covers trigger, scope, sibling routing, return semantics, and interpretive caveats. Nothing an agent needs in order to call it correctly 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% and the Args block largely restates the schema wording verbatim, so the description adds no meaning beyond it. The one useful addition — 'Do not invent one' for listing_id and the valid language set — is already present in the schema. Baseline 3 applies.

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 (find homes similar to one listing) plus explicit scope: 'in its own market'. It immediately contrasts with the named sibling `find_similar_elsewhere`, so the agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Use when the user likes a home and wants more like it nearby') with sample user phrasings, and names the alternative tool and the condition that selects it (another city). Both the when and the when-not are stated.

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.

Resources