Cenogram - Polish Real Estate Data

estimate_land_value

Read-only

[Beta] Estimate the market value of an undeveloped plot of land from comparable registered transaction prices near a point. An orientation estimate, NOT a certified appraisal (operat szacunkowy) — it 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 (the plot size in m², 100–1000000) is REQUIRED with lat/lng; with parcelId it defaults to the parcel's area from the cadastre when omitted. landType selects the comparable segment: plot (a building plot, default) or agricultural (farmland) — the caller chooses it; we do not infer the subject plot's designation. Optional mpzpDesignation narrows the comparables to a recorded land designation; includeComps (default true) echoes the nearest comparables it weighed. Returns the estimate per m² and per hectare, 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 areas with different as_of. Comparables are chosen by the land designation recorded in the transaction register for their parcels (not a local zoning plan, and with no guarantee it matches each comparable's date); this does not assert the subject plot is buildable. Undeveloped land only (v1). Too few comparables near the point, or an area that cannot be determined → no estimate (the credit is refunded). Costs 5 API tokens, refunded when no estimate is produced. This feature can be switched off for maintenance; when it is, the call returns a plain "temporarily unavailable" message rather than an estimate. 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 plot (WGS84, Poland). Must be paired with lng. Use this OR parcelId. area is required on this path.
`lng`	No	Longitude of the plot (WGS84, Poland). Must be paired with lat. Use this OR parcelId. area is required on this path.
`area`	No	Plot area in m² (100–1000000 = 100 m² to 100 ha). REQUIRED with lat/lng; optional with parcelId (read from the cadastre when omitted).
`landType`	No	Comparable segment: plot (a building plot, default) or agricultural (farmland). The caller chooses it.
`parcelId`	No	Full cadastral id (slash or dash form) or internal UUID; the parcel centroid is used and area defaults to the cadastre when omitted. Use instead of lat/lng.
`includeComps`	No	Echo the nearest comparables the estimate weighed (default true). Set false for the estimate only.
`mpzpDesignation`	No	Narrow the comparables to a recorded land-designation token (e.g. 'budownictwoMieszkanioweJednorodzinne'); 'unknown' matches rows with no designation recorded (optional).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well past the readOnlyHint/destructiveHint annotations: it discloses that this is a beta orientation estimate not a certified appraisal, the 5-token cost with refund on no-estimate, maintenance switch-off behavior, as_of county-level freshness, and that non-market deeds are excluded from price aggregates. Rich, non-obvious behavioral context.

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-loads the purpose and key constraints, and most sentences carry real information. It is dense and lengthy, with some hard-to-parse clauses (the comparables-selection sentence) and a tangential closing note on price aggregates that slightly dilute the structure.

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, so the description carries the return-shape burden and does: estimate per m² and per hectare, likely and wide range, confidence band, comparable count, and as_of date. Given a complex 7-param tool, this is complete enough for an agent to call and interpret results 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 description coverage is already 100%, so the baseline is 3. The description nonetheless adds semantic value: that landType is caller-chosen and not inferred, that mpzpDesignation narrows the comparable set, and that area falls back to the cadastre on the parcelId path — clarifying intent beyond the field docs.

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 precise verb+resource ('Estimate the market value of an undeveloped plot of land from comparable registered transaction prices near a point') and scopes it tightly ('Undeveloped land only (v1)'). An agent can distinguish this land-specific estimator from the general estimate_value sibling without opening the schema.

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?

Provides clear usage context: address by lat/lng OR parcelId (exactly one), area required on the coordinate path, and the 'undeveloped land only' constraint. It stops short of explicitly naming alternatives (e.g., estimate_value for built property), so routing guidance is contextual rather than prescriptive.

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?