Cenogram - Polish Real Estate Data
Server Details
7M+ real estate transactions from Poland's RCN registry. Search, compare, and analyze prices.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.6/5 across 27 of 27 tools scored. Lowest: 3.7/5.
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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
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
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.
Discussions
No comments yet. Be the first to start the discussion!