Skip to main content
Glama
Sign In

Cenogram - Polish Real Estate Data

by pl.cenogram.mcp
OverviewDiscussionsAdmin

estimate_value

Read-only

[Beta] Estimate an apartment's market value from comparable registered transaction prices near a point. An orientation estimate, NOT a certified appraisal: it ignores condition, finish standard and floor. Address by lat + lng OR parcelId (the parcel centroid is used) - exactly one. area (usable m², 10–250) is REQUIRED. Returns the point estimate, a likely and a wide range, a confidence band, the comparable count and an as_of date (lags by county: NOT comparable across cities with different as_of). Apartments only; for a building plot or farmland use estimate_land_value. Too few comparables → no estimate. Costs 5 API tokens, refunded when none is produced. Aggregates exclude fractional shares and non-market deeds.

Input Schema

NameRequiredDescriptionDefault
latNoApartment latitude (WGS84); pair with lng. This OR parcelId.
lngNoApartment longitude (WGS84); pair with lat. This OR parcelId.
areaYesApartment usable area in m² (REQUIRED, 10–250).
roomsNoRoom count (1–10); narrows comparables to ±1 room.
marketNoRestrict comparables to the primary (new-build) or secondary market.
parcelIdNoFull cadastral id (slash or dash form) or internal UUID; the parcel centroid is used. Instead of lat/lng.
includeCompsNoEcho the comparables weighed (default true); false = estimate only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude of the apartment (WGS84, Poland); pair with lng. Use this OR parcelId."New value: +"Apartment latitude (WGS84); pair with lng. This OR parcelId."
    • changedInput schema / properties / lng / description
      Previous value: -"Longitude of the apartment (WGS84, Poland); pair with lat. Use this OR parcelId."New value: +"Apartment longitude (WGS84); pair with lat. This OR parcelId."
  2. Changed7 schema fields changed
    • changedInput schema / properties / area / description
      Previous value: -"Apartment usable area in m² (REQUIRED, 10–250). Estimates for 300+ m² are unreliable and rejected."New value: +"Apartment usable area in m² (REQUIRED, 10–250)."
    • changedInput schema / properties / includeComps / description
      Previous value: -"Echo the nearest comparables the estimate weighed (default true). Set false for the estimate only."New value: +"Echo the comparables weighed (default true); false = estimate only."
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude of the apartment (WGS84, Poland). Must be paired with lng. Use this OR parcelId."New value: +"Latitude of the apartment (WGS84, Poland); pair with lng. Use this OR parcelId."
    • changedInput schema / properties / lng / description
      Previous value: -"Longitude of the apartment (WGS84, Poland). Must be paired with lat. Use this OR parcelId."New value: +"Longitude of the apartment (WGS84, Poland); pair with lat. Use this OR parcelId."
    • changedInput schema / properties / market / description
      Previous value: -"Restrict comparables to the primary (new-build) or secondary market (optional)."New value: +"Restrict comparables to the primary (new-build) or secondary market."
    • changedInput schema / properties / parcelId / description
      Previous value: -"Full cadastral id (slash or dash form) or internal UUID; the parcel centroid is used. Use instead of lat/lng."New value: +"Full cadastral id (slash or dash form) or internal UUID; the parcel centroid is used. Instead of lat/lng."
    • changedInput schema / properties / rooms / description
      Previous value: -"Room count (1–10, optional) — narrows the comparables to ±1 room."New value: +"Room count (1–10); narrows comparables to ±1 room."
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

With annotations already declaring readOnly/non-destructive/openWorld=false, the description still adds substantial context beyond them: the not-a-certified-appraisal caveat and what it ignores (condition, finish standard, floor), the beta status, the comparability limitation of as_of lags across counties, the cost of 5 API tokens with refund on no-estimate, and the exclusion of fractional shares and non-market deeds. This is unusually complete disclosure for a read-only tool.

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?

Dense but well front-loaded: purpose first, then addressing rules, then return shape, then sibling routing and cost. Every sentence carries information, though the parenthetical caveats make it slightly heavy to parse in one pass.

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?

No output schema exists, and the description compensates fully by naming the return components (point estimate, likely and wide range, confidence band, comparable count, as_of). Combined with the cost model, the minimum-data failure mode, and the sibling alternative, nothing needed to invoke it correctly is missing.

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 the baseline is 3, but the description adds real meaning the schema cannot express: the mutual exclusivity of lat/lng and parcelId ('exactly one') and that the parcel centroid is used when parcelId is supplied. It also reinforces that area is REQUIRED, though the schema already marks it.

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 ('Estimate an apartment's market value from comparable registered transaction prices near a point') and immediately scopes it as apartments only, naming estimate_land_value for the alternatives. An agent can distinguish it from the land-estimation sibling without opening any 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 explicit routing rules: 'Apartments only; for a building plot or farmland use estimate_land_value', plus the addressing rule 'lat + lng OR parcelId - exactly one' and the failure condition 'Too few comparables → no estimate'. These are exactly the when-to-use and when-not-to-use signals an agent needs.

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 toolsInspect
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