Skip to main content
Glama

Cubi Estate

Get price history

get_price_history
Read-only

Has this home's asking price changed? Every change Cubi observed.

Returns each observed asking-price change for one listing (date, old and
new price, percent), oldest first, with the current price, the total
change since the first observed price, and when Cubi first saw the
listing. Cubi's log starts on `tracked_since` (2026-05-02): no change
listed means none was observed since then, not that the price never
changed — say so. Asking prices, not sale prices or valuations.

Args:
    listing_id: Source-prefixed id of a listing already shown (e.g.
        `remax:12345`). Do not invent one.

Returns:
    JSON: current_price, on_cubi_since, tracked_since, changes[{date,
    old_price, new_price, pct}], drops, raises, total_change_pct.

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": "get_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. Changed1 schema field changed
    • 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

A3.6/5.0
Behavior3/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), so the bar is lower; the description still adds meaningful context on the observation window (tracked_since 2026-05-02) and the critical caveat that absence of changes means none were observed in that window, not that none occurred. It does not mention whether the history is paginated or how far back the log can be trusted beyond the fixed start date, but for a read-only lookup the behavioral picture is adequate.

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 opening question plus answer is front-loaded and the caveat about the tracking window is prominent. The Args block duplicates the input schema and the Returns block duplicates the existing output schema, which is mild redundancy rather than bloat.

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 single-parameter read-only lookup with a full output schema, everything the agent needs is present: what is returned, ordering, the scope of the observation window, and the interpretive caveat. The only remaining explanation is return shape, which the output schema already supplies.

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 verbatim ('Source-prefixed id of a listing already shown ... Do not invent one'), adding no new meaning. With the schema doing all the work, a baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — the observed asking-price change history for one listing — and explicitly draws the line between asking prices and sale prices or valuations. It doesn't name a sibling such as compare_asking_prices to route the agent, but 'for one listing' implicitly scopes it away from the comparison tools.

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

Usage Guidelines3/5

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

Usage context is implied ('Has this home's asking price changed?') and there is a valuable instruction on how to report empty results: 'say so' rather than claiming the price never changed. There is no explicit when-to-use vs when-to-use-an-alternative guidance, so the agent must infer that this is the per-listing drill-down rather than the cross-listing comparison.

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