Cenogram - Polish Real Estate Data

estimate_value

Read-only

[Beta] Estimate the market value of an apartment from comparable registered transaction prices near a point. An orientation estimate, NOT a certified appraisal (operat szacunkowy) — it does not account for the unit's condition, finish standard or floor, and does not replace a surveyor's valuation. Address by lat + lng (a point on the map) OR parcelId (a full cadastral id or internal UUID; the parcel centroid is used) — exactly one. area (usable area in m², 10–250) is REQUIRED: there is no per-address floor-area source in Poland, so the caller supplies it. Optional: rooms (1–10) and market (primary/secondary) narrow the comparables; includeComps (default true) echoes the nearest comparables it weighed. Returns the point estimate, a likely and a wide value range, a confidence band, the comparable count, and an as_of date. as_of reflects transaction-data freshness, which lags by county — estimates are NOT directly comparable across cities with different as_of. Apartments only (v1), 10–250 m². For undeveloped land (a building plot or farmland), use estimate_land_value. Too few comparables near the point → no estimate (the credit is refunded). Costs 5 API tokens, refunded when no estimate is produced. Note: median/average prices are market-based — fractional ownership shares and non-market deeds (public tenders, foreclosures, privileged/subsidized sales) are excluded from price aggregates. Transaction counts and coverage stay complete.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No	Latitude of the apartment (WGS84, Poland). Must be paired with lng. Use this OR parcelId.
`lng`	No	Longitude of the apartment (WGS84, Poland). Must be paired with lat. Use this OR parcelId.
`area`	Yes	Apartment usable area in m² (REQUIRED, 10–250). Estimates for 300+ m² are unreliable and rejected.
`rooms`	No	Room count (1–10, optional) — narrows the comparables to ±1 room.
`market`	No	Restrict comparables to the primary (new-build) or secondary market (optional).
`parcelId`	No	Full cadastral id (slash or dash form) or internal UUID; the parcel centroid is used. Use instead of lat/lng.
`includeComps`	No	Echo the nearest comparables the estimate weighed (default true). Set false for the estimate only.

Schema Changelog

Changes observed during successful MCP inspections.

AddedJul 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare readOnlyHint/destructiveHint, so the description carries the real behavioral burden and does so: cost of 5 API tokens with refund on failure, the no-estimate case when comparables are too few, as_of freshness lagging by county and non-comparability across cities, and exclusion of fractional/non-market deeds from price aggregates.

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 purpose and the appraisal disclaimer, then inputs, then return shape, then costs. Dense and mostly waste-free, though the closing note on median/average price exclusions is somewhat tangential to invoking this 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?

With no output schema, the description enumerates the return contents (point estimate, likely/wide ranges, confidence band, comparable count, as_of). Inputs, cost, failure mode, and scope limits are all covered, so an agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds genuine meaning: why area is required (no per-address floor-area source in Poland), that rooms narrows comparables to ±1, that the parcel centroid is used for parcelId, and includeComps' default/echo behavior.

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 (estimate) and resource (market value of an apartment) plus the method (comparable registered transaction prices near a point). It explicitly distinguishes itself from the sibling estimate_land_value and scopes itself to apartments only.

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 explicit when-to-use (apartments, 10–250 m²), when-not (undeveloped land → estimate_land_value), input exclusivity (lat+lng OR parcelId, exactly one), and caveats about what it does not do (no condition/floor, not a certified appraisal). Nothing about tool selection 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 Cenogram - Polish Real Estate Data 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?