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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No		en
`listing_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare a safe read operation (readOnlyHint=true, destructiveHint=false), and the description adds real behavioral context: the percentile band definition, the not-found/no-range case with an explicit 'do not invent one' instruction, and the framing caveat to relay that this is asking prices, not a valuation.

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 comparison, then Args and Returns blocks. Efficient overall, though the Returns block partially restates what the output schema already declares, making it slightly longer than strictly necessary.

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 read-only two-parameter comparison tool with an output schema present, the description covers purpose, preconditions, edge cases, and relaying caveats. Nothing an agent needs to call and interpret it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so: listing_id is a source-prefixed id from a prior search that must not be invented, and lang is an ISO 639-1 code with an explicit enumerated value set and default. This fully compensates for the empty schema descriptions.

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: comparing one listing's asking price against comparable active listings in the same city. It explicitly distinguishes itself from valuation and sale-price prediction, so an agent will not confuse it with search_properties or get_listing.

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 implies the correct usage context ('listing_id from a prior search result') and states the no-comparables case. It doesn't explicitly name a sibling alternative, but the preconditions and edge-case handling are clear.

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?