7M+ real estate transactions from Poland's RCN registry. Search, compare, and analyze prices.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
get_parcel_reportestimate_valueget_transaction_farmlandresolve_parcelget_transaction_planningget_price_spread1 field changedInput schema / properties / location / descriptionPrevious value: -"City name, resolves to a county (e.g. 'Warszawa', 'Kraków', 'Gdańsk'). Use this OR teryt."New value: +"County-level city name — must be a miasto na prawach powiatu or a catalog entry from list_price_spread_locations (e.g. 'Warszawa', 'Kraków', 'Gdańsk'). A town within a larger powiat, a non-Warszawa district, or an osiedle will 404 — check the catalog or use teryt first. Use this OR teryt."get_rental_yield1 field changedInput schema / properties / location / descriptionPrevious value: -"City name, resolves to a county (e.g. 'Warszawa', 'Kraków', 'Gdańsk'). Use this OR teryt."New value: +"County-level city name — must be a miasto na prawach powiatu or a catalog entry from list_rental_yield_locations (e.g. 'Warszawa', 'Kraków', 'Gdańsk'). A town within a larger powiat, a non-Warszawa district, or an osiedle will 404 — check the catalog or use teryt first. Use this OR teryt."compare_locations1 field changedInput schema / properties / floorAdded value: +{
+ "description": "Floor of the unit (piętro lokalu, residential). Multi-select buckets: exact integers incl. '0' (parter) and negatives e.g. '-1' (basement), 'Nplus' e.g. '10plus' = 10 or more, '0plus' = ground and above, 'unknown' = no floor recorded (NULL). E.g. ['0','1','2'] for ground-to-2nd floor. Building storeys are a different attribute. Without 'unknown', rows with no floor are excluded.",
+ "items": {
+ "pattern": "^(-?\\d+|\\d+plus|unknown)$",
+ "type": "string"
+ },
+ "type": "array"
+}search_by_area1 field changedInput schema / properties / floorAdded value: +{
+ "description": "Floor of the unit (piętro lokalu, residential). Multi-select buckets: exact integers incl. '0' (parter) and negatives e.g. '-1' (basement), 'Nplus' e.g. '10plus' = 10 or more, '0plus' = ground and above, 'unknown' = no floor recorded (NULL). E.g. ['0','1','2'] for ground-to-2nd floor. Building storeys are a different attribute. Without 'unknown', rows with no floor are excluded.",
+ "items": {
+ "pattern": "^(-?\\d+|\\d+plus|unknown)$",
+ "type": "string"
+ },
+ "type": "array"
+}search_by_polygon1 field changedInput schema / properties / floorAdded value: +{
+ "description": "Floor of the unit (piętro lokalu, residential). Multi-select buckets: exact integers incl. '0' (parter) and negatives e.g. '-1' (basement), 'Nplus' e.g. '10plus' = 10 or more, '0plus' = ground and above, 'unknown' = no floor recorded (NULL). E.g. ['0','1','2'] for ground-to-2nd floor. Building storeys are a different attribute. Without 'unknown', rows with no floor are excluded.",
+ "items": {
+ "pattern": "^(-?\\d+|\\d+plus|unknown)$",
+ "type": "string"
+ },
+ "type": "array"
+}search_transactions1 field changedInput schema / properties / floorAdded value: +{
+ "description": "Floor of the unit (piętro lokalu, residential). Multi-select buckets: exact integers incl. '0' (parter) and negatives e.g. '-1' (basement), 'Nplus' e.g. '10plus' = 10 or more, '0plus' = ground and above, 'unknown' = no floor recorded (NULL). E.g. ['0','1','2'] for ground-to-2nd floor. Building storeys are a different attribute. Without 'unknown', rows with no floor are excluded.",
+ "items": {
+ "pattern": "^(-?\\d+|\\d+plus|unknown)$",
+ "type": "string"
+ },
+ "type": "array"
+}get_infrastructure_signalsget_transaction_permitsget_price_spread1 field changedInput schema / properties / teryt / descriptionPrevious value: -"TERYT county code (4 digits, e.g. 1465 = Warszawa). Longer codes (gmina/precinct) are truncated to the county. Wins over location when both are provided."New value: +"TERYT code. 4 digits = county (e.g. 1465 = Warszawa). 6 digits = dzielnica where available (today: Warszawa's 18 districts, e.g. 146510 = Śródmieście) → spread for that district. Other longer codes (gmina/precinct) are truncated to the county. Wins over location when both are provided."get_rental_yield1 field changedInput schema / properties / teryt / descriptionPrevious value: -"TERYT county code (4 digits, e.g. 1465 = Warszawa). Longer codes (gmina/precinct) are truncated to the county. Wins over location when both are provided."New value: +"TERYT code. 4 digits = county (e.g. 1465 = Warszawa). 6 digits = dzielnica where available (today: Warszawa's 18 districts, e.g. 146510 = Śródmieście) → yield for that district. Other longer codes (gmina/precinct) are truncated to the county. Wins over location when both are provided."get_price_spreadget_rental_yieldlist_price_spread_locationslist_rental_yield_locationsget_transaction_transitcompare_locations1 field changedInput schema / properties / ownershipTypeAdded value: +{
+ "description": "Ownership / legal-right type filter (rodzaj prawa do nieruchomości). land_ownership; perpetual_usufruct (użytkowanie wieczyste — covers both registry codes for this right); cooperative_ownership; unit_sale; ownership; unit_ownership_with_appurtenant_right; building_ownership_with_appurtenant_right. 'unknown' = no right recorded (NULL). Multi-select; e.g. ['land_ownership','perpetual_usufruct'] to compare ownership vs perpetual usufruct on undeveloped land.",
+ "items": {
+ "enum": [
+ "land_ownership",
+ "perpetual_usufruct",
+ "cooperative_ownership",
+ "unit_sale",
+ "ownership",
+ "unit_ownership_with_appurtenant_right",
+ "building_ownership_with_appurtenant_right",
+ "unknown"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+}search_by_area1 field changedInput schema / properties / ownershipTypeAdded value: +{
+ "description": "Ownership / legal-right type filter (rodzaj prawa do nieruchomości). land_ownership; perpetual_usufruct (użytkowanie wieczyste — covers both registry codes for this right); cooperative_ownership; unit_sale; ownership; unit_ownership_with_appurtenant_right; building_ownership_with_appurtenant_right. 'unknown' = no right recorded (NULL). Multi-select; e.g. ['land_ownership','perpetual_usufruct'] to compare ownership vs perpetual usufruct on undeveloped land.",
+ "items": {
+ "enum": [
+ "land_ownership",
+ "perpetual_usufruct",
+ "cooperative_ownership",
+ "unit_sale",
+ "ownership",
+ "unit_ownership_with_appurtenant_right",
+ "building_ownership_with_appurtenant_right",
+ "unknown"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+}search_by_polygon1 field changedInput schema / properties / ownershipTypeAdded value: +{
+ "description": "Ownership / legal-right type filter (rodzaj prawa do nieruchomości). land_ownership; perpetual_usufruct (użytkowanie wieczyste — covers both registry codes for this right); cooperative_ownership; unit_sale; ownership; unit_ownership_with_appurtenant_right; building_ownership_with_appurtenant_right. 'unknown' = no right recorded (NULL). Multi-select; e.g. ['land_ownership','perpetual_usufruct'] to compare ownership vs perpetual usufruct on undeveloped land.",
+ "items": {
+ "enum": [
+ "land_ownership",
+ "perpetual_usufruct",
+ "cooperative_ownership",
+ "unit_sale",
+ "ownership",
+ "unit_ownership_with_appurtenant_right",
+ "building_ownership_with_appurtenant_right",
+ "unknown"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+}search_transactions1 field changedInput schema / properties / ownershipTypeAdded value: +{
+ "description": "Ownership / legal-right type filter (rodzaj prawa do nieruchomości). land_ownership; perpetual_usufruct (użytkowanie wieczyste — covers both registry codes for this right); cooperative_ownership; unit_sale; ownership; unit_ownership_with_appurtenant_right; building_ownership_with_appurtenant_right. 'unknown' = no right recorded (NULL). Multi-select; e.g. ['land_ownership','perpetual_usufruct'] to compare ownership vs perpetual usufruct on undeveloped land.",
+ "items": {
+ "enum": [
+ "land_ownership",
+ "perpetual_usufruct",
+ "cooperative_ownership",
+ "unit_sale",
+ "ownership",
+ "unit_ownership_with_appurtenant_right",
+ "building_ownership_with_appurtenant_right",
+ "unknown"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+}get_transaction_heritagesearch_by_area1 field changedInput schema / properties / heritageStatusAdded value: +{
+ "description": "Heritage-listing filter. listed = a protected monument on/at the property's land; zone = the land lies within a protected urban layout or the designated surroundings of a monument. Selects ONLY transactions where a listing was detected; absence of a detection is never asserted as 'not listed'. Multi-select; e.g. ['listed'] = individually listed properties only.",
+ "items": {
+ "enum": [
+ "listed",
+ "zone"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+}search_transactions1 field changedInput schema / properties / heritageStatusAdded value: +{
+ "description": "Heritage-listing filter. listed = a protected monument on/at the property's land; zone = the land lies within a protected urban layout or the designated surroundings of a monument. Selects ONLY transactions where a listing was detected; absence of a detection is never asserted as 'not listed'. Multi-select; e.g. ['listed'] = individually listed properties only.",
+ "items": {
+ "enum": [
+ "listed",
+ "zone"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+}get_transaction_landslidesearch_by_area1 field changedInput schema / properties / landslideRiskAdded value: +{
+ "description": "Landslide-hazard filter, from official landslide-hazard maps (1:10,000 scale). 'landslide' = the land intersects a mapped landslide area; 'threatened' = an area threatened by mass movements. Selects ONLY transactions whose land intersects a mapped hazard area — an intersection means overlap with a mapped area, not that the parcel itself is a landslide; absence of a zone is never asserted as 'safe'. Multi-select; e.g. ['landslide','threatened'] = any mapped hazard.",
+ "items": {
+ "enum": [
+ "landslide",
+ "threatened"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+}search_transactions1 field changedInput schema / properties / landslideRiskAdded value: +{
+ "description": "Landslide-hazard filter, from official landslide-hazard maps (1:10,000 scale). 'landslide' = the land intersects a mapped landslide area; 'threatened' = an area threatened by mass movements. Selects ONLY transactions whose land intersects a mapped hazard area — an intersection means overlap with a mapped area, not that the parcel itself is a landslide; absence of a zone is never asserted as 'safe'. Multi-select; e.g. ['landslide','threatened'] = any mapped hazard.",
+ "items": {
+ "enum": [
+ "landslide",
+ "threatened"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+}get_transaction_surroundingsClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Add one secure layer between your agents and this server.
All 27 tools have clearly distinct purposes with thorough descriptions. Despite many tools dealing with similar domains (e.g., price statistics vs. price distribution vs. price spread), each targets a different aspect or output format. The get_transaction_* tools each cover a unique enrichment layer, and search tools are distinguished by spatial method. No two tools are easily confused.
Naming largely follows a verb_noun pattern: 'get_' for data retrieval, 'list_' for enumeration, 'search_' for transaction queries, with a few exceptions like 'compare_locations', 'estimate_value', 'resolve_parcel'. The deviations are sensible and intuitive, but the set is not perfectly uniform (e.g., 'list_price_spread_locations' vs 'list_locations'). Overall consistent and predictable.
27 tools is on the high side but appropriate given the complexity of the Polish real estate domain. The tool set covers parcel data, transactions, demographics, infrastructure, price analytics, and multiple enrichment layers. While some consolidation might be possible, each tool serves a distinct analytical need and the count does not feel bloated.
The surface is remarkably comprehensive, covering transaction search (by filters, area, polygon), parcel reports, price analysis, demographic/infrastructure data, and numerous parcel enrichment layers. Minor gaps exist, such as no direct property-to-property comparison (only area-level via compare_locations) and no rental market data beyond yield estimation, but the core workflows (discover, evaluate, due diligence) are well supported.