Cubi Estate

Compare asking prices

compare_asking_prices

Read-only

Compare one listing's asking price with comparable homes on Cubi.

Returns the range of ASKING prices of comparable active listings in the
same city (25th-75th percentile, with the number of comparables) and
where this listing's own asking price sits against it: below, within or
above. This is a comparison of asking prices, not a valuation and not a
prediction of the sale price — say so when you relay it. When too few
comparables exist, no range is returned; do not invent one.

Args:
    listing_id: Source-prefixed listing id from a prior search result
        (e.g. `remax:12345`). Do not invent one.
    lang: ISO 639-1 language code (en/pt/es/fr/de/nl/ru). Defaults to en.

Returns:
    JSON with asking_price, band {low, median, high}, n_comps,
    asking_vs_band, and links to continue on Cubi — 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": "compare_asking_prices"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	ISO 639-1 language code (en/pt/es/fr/de/nl/ru). Defaults to en.	en
`listing_id`	Yes	Source-prefixed listing id from a prior search result (e.g. `remax:12345`). Do not invent one.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 11, 2026

addedInput schema / properties / lang / description

Added value: +"ISO 639-1 language code (en/pt/es/fr/de/nl/ru). Defaults to en."

addedInput schema / properties / listing_id / description

Added value: +"Source-prefixed listing id from a prior search result (e.g. `remax:12345`). Do not invent one."

First observedOct 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, non-destructive and non-open-world, and the description adds genuinely new behavioral detail: the 25th-75th percentile methodology, that no range is returned when comparables are insufficient, and the explicit instruction not to invent one. It does not mention pagination, rate limits, or error semantics beyond 'not-found', keeping it short of a 5.

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 core operation and the key caveat before any parameter detail, and every sentence carries information. The Args and Returns blocks duplicate the input schema and output schema respectively, which is mild redundancy rather than waste.

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?

For a two-parameter read-only tool with an output schema, the description covers purpose, method, output fields at a summary level, and the degenerate case of too few comparables. The omitted pieces (other failure modes, link contents) are adequately handled by the output schema and annotations.

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 description's Args block repeats the schema text almost verbatim (listing_id origin, lang enum list and default). The 'do not invent one' constraint on provenance is valuable but already present in the schema, so no meaning is added beyond structured data.

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 ('Compare one listing's asking price with comparable homes') and immediately narrows scope by excluding valuation and sale-price prediction. An agent can tell exactly what this computes and what it does not.

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?

Gives clear when-to-use context and an important when-not caveat ('not a valuation and not a prediction of the sale price'), plus an instruction for relaying results. It does not name any specific sibling tool (e.g. find_similar_homes or compare_inventory) as an alternative, so differentiation from the catalog is left to inference.

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

All Cubi Estate 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.

Resources

Need Help?