ceny-nieruchomosci-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CENY_STATS | No | Set to 1 to enable anonymous usage counters exposed under /stats | 1 |
| CENY_CONTACT | No | Contact information for the server operator | |
| CENY_CACHE_MB | No | Cache size in megabytes | 300 |
| CENY_PUBLIC_URL | No | Public URL of the server | |
| CENY_RATE_LIMIT | No | Rate limit setting for the server | |
| CENY_MAX_RADIUS_M | No | Maximum search radius in meters | 1500 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| property_pricesA | Actual sale prices of flats, houses or building plots near a place in Poland, from notarial deeds (official Rejestr Cen Nieruchomości). Returns median price per m², interquartile range, typical total price and area, breakdown by rooms, yearly trend and recent transactions. place: address "Poznań, Garbary 10", street "Kraków, Długa", town "Swarzędz" or "lat,lon". |
| parcel_reportA | Everything public about one land parcel (działka) in Poland: parcel id, area and land-use class from the land register (EGiB), local zoning plan (MPZP) and zoning symbol, utility networks on or near the plot (water, sewer, gas, power, heat, telecom – GESUT), flood hazard (ISOK maps), nature protection areas (GDOŚ) and plot prices nearby (RCN). query: parcel id "302109_4.0001.100", "obręb number" like "Bnin 100" or "obręb Bnin działka 100 gmina Kórnik", an address "Kórnik, Poznańska 1" (the parcel under the address point) or "lat,lon". |
| find_addressA | Resolve a Polish address, street or town to coordinates using the official address register (GUGiK). Useful to check which place property_prices will use. |
| data_sourcesB | Where the data comes from, licence and caveats. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
find_address and data_sources are clearly distinct, while property_prices and parcel_report have some overlap because both can return nearby land/plot prices. property_prices also accepts address input directly, which slightly weakens the need for find_address, but the descriptions still make each tool's primary intent identifiable.
All names use snake_case, which is consistent and readable. However, find_address is verb_noun while property_prices, parcel_report, and data_sources are noun phrases, so the set mixes naming conventions rather than following one predictable pattern.
Four tools is a well-scoped surface for a focused Polish property-data lookup server. Each tool has a plausible role: geocoding, price statistics, parcel due diligence, and provenance/caveats.
The surface covers the core workflow: resolve an address, inspect market prices, pull a full parcel report, and check data sources. Minor gaps remain, such as no individual building/flat detail lookup or bulk multi-location comparison, but agents can work around these for the stated purpose.