Cenogram - Polish Real Estate Data

get_flood_risk

Read-only

EXPERIMENTAL (beta): may change or be withdrawn; no critical workflows on it. What share of a Polish county's real-estate transactions sit on land in a mapped flood-hazard zone, by severity, from the RCN registry. Bands are return periods: high = most frequent (~1-in-10-year), medium ~1-in-100, low = rarest (~1-in-500). Counts land in a mapped zone only; absence of a zone is never asserted as 'safe' (an area may be unmapped). All-time, no date window; suppressed below 5 assessed transactions. Coverage is county-level: unless the location is a major city you know is covered, call list_coverage(metric="flood_risk") FIRST or pass a 4-digit county TERYT.

Input Schema

Name	Required	Description	Default
`teryt`	No	TERYT code. 4 digits = county (e.g. 1465 = Warszawa). Longer codes (gmina/precinct/district) resolve to the county. Wins over location.
`location`	No	City or county name (e.g. 'Warszawa', 'Gdańsk'). District and gmina names are accepted ('Kraków-Podgórze', 'Wieliczka'), answered at the parent county with a note; a gmina name shared by counties returns candidates. A town within a larger powiat or an osiedle may 404 - check the catalog or use teryt. This OR teryt.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

changedInput schema / properties / location / description

Previous value: -"City or county name (e.g. 'Warszawa', 'Gdańsk'). District and gmina names are accepted ('Kraków-Podgórze', 'Wieliczka') but coverage is county-level, so the answer is the parent county with a note. A gmina name shared by counties returns candidates. A town within a larger powiat or an osiedle may 404 - check the catalog or use teryt. This OR teryt."New value: +"City or county name (e.g. 'Warszawa', 'Gdańsk'). District and gmina names are accepted ('Kraków-Podgórze', 'Wieliczka'), answered at the parent county with a note; a gmina name shared by counties returns candidates. A town within a larger powiat or an osiedle may 404 - check the catalog or use teryt. This OR teryt."

Changed2 schema fields changedOct 23, 2026

changedInput schema / properties / location / description

Previous value: -"County-level city/county name (e.g. 'Warszawa', 'Kraków', 'Gdańsk'). District names are accepted (a Warszawa district or another city's delegatura, e.g. 'Kraków-Podgórze'), and so are gmina names (e.g. 'Wieliczka'), but coverage is county-level, so the answer is the parent county with a note. A gmina name shared by counties returns the candidates with their codes. A town within a larger powiat or an osiedle may 404 — check the catalog or use teryt first. Use this OR teryt."New value: +"City or county name (e.g. 'Warszawa', 'Gdańsk'). District and gmina names are accepted ('Kraków-Podgórze', 'Wieliczka') but coverage is county-level, so the answer is the parent county with a note. A gmina name shared by counties returns candidates. A town within a larger powiat or an osiedle may 404 - check the catalog or use teryt. This OR teryt."

changedInput schema / properties / teryt / description

Previous value: -"TERYT code. 4 digits = county (e.g. 1465 = Warszawa). Longer codes (gmina/precinct/district) are truncated/resolved to the county. Wins over location when both are provided."New value: +"TERYT code. 4 digits = county (e.g. 1465 = Warszawa). Longer codes (gmina/precinct/district) resolve to the county. Wins over location."

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / location / description

Previous value: -"County-level city/county name (e.g. 'Warszawa', 'Kraków', 'Gdańsk'). District names are accepted (a Warszawa district or another city's delegatura, e.g. 'Kraków-Podgórze'), but coverage is county-level, so the answer is the parent county with a note. A town within a larger powiat or an osiedle may 404 — check the catalog or use teryt first. Use this OR teryt."New value: +"County-level city/county name (e.g. 'Warszawa', 'Kraków', 'Gdańsk'). District names are accepted (a Warszawa district or another city's delegatura, e.g. 'Kraków-Podgórze'), and so are gmina names (e.g. 'Wieliczka'), but coverage is county-level, so the answer is the parent county with a note. A gmina name shared by counties returns the candidates with their codes. A town within a larger powiat or an osiedle may 404 — check the catalog or use teryt first. Use this OR teryt."

Changed1 schema field changedSep 20, 2026

changedInput schema / properties / location / description

Previous value: -"County-level city/county name (e.g. 'Warszawa', 'Kraków', 'Gdańsk'). A town within a larger powiat or an osiedle may 404 — check the catalog or use teryt first. Use this OR teryt."New value: +"County-level city/county name (e.g. 'Warszawa', 'Kraków', 'Gdańsk'). District names are accepted (a Warszawa district or another city's delegatura, e.g. 'Kraków-Podgórze'), but coverage is county-level, so the answer is the parent county with a note. A town within a larger powiat or an osiedle may 404 — check the catalog or use teryt first. Use this OR teryt."

AddedSep 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly, non-destructive, closed-world, but the description adds substantive behavior: all-time with no date window, suppression below 5 assessed transactions, counting only land inside a mapped zone, and the explicit refusal to assert safety from absence of a zone. Those caveats are not recoverable from the annotations and materially change how an agent should interpret results.

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 experimental warning, then purpose, then band definitions, then caveats, then the routing hint. It is dense but each sentence carries information; the band definitions and the 'not safe' caveat are the only parts that could be tightened.

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 still conveys the return shape (share by severity band), the time scope, the suppression threshold, and the interpretation limits. For a two-parameter read-only metric tool, an agent has everything needed to call it and read the result correctly.

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 coverage is 100% and both parameters are fully documented in the schema, including TERYT length rules and location fallback behavior. The description reinforces the county-level resolution constraint but adds little syntax or format detail beyond what the schema already provides, so the baseline of 3 applies.

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 measure (share of a Polish county's real-estate transactions on land in a mapped flood-hazard zone, by severity) plus the data source (RCN registry). The severity bands are defined inline as return periods, so an agent knows exactly what the tool produces and how it differs from siblings like get_transaction_layer or get_parcel_land_class.

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 an explicit prerequisite workflow: call list_coverage(metric="flood_risk") first or pass a 4-digit county TERYT unless the location is a known major city. It also names the alternative (list_coverage) and states the condition that selects it, plus the beta/experimental caveat about critical workflows.

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?