cenogram-mcp-serverofficial
A
licenseA
qualityC
maintenance7M+ real estate transactions from Poland's RCN registry. Search, compare, and analyze prices
23
136
1
MIT
realestate
Server Details
Czech distressed real estate — anonymized district aggregates (k≥5). Free tier.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- martinhavel/cz-agents-mcp
- GitHub Stars
- 5
- Server Listing
- cz-agents-mcp
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
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.
100% free. Your data is private.
Tool Definition Quality
A4.3/5.0
Tool DescriptionsA
Average 4.5/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no possibility of confusion or overlap. The tool's purpose is clearly defined and distinct.
Naming Consistency5/5
The single tool name follows a clear, descriptive verb_noun pattern. With only one tool, there is no inconsistency to assess.
Tool Count3/5
The server has only one tool, which feels thin for a general real estate data domain. However, a single aggregate query tool could be appropriate if the server's scope is intentionally narrow.
Completeness2/5
The tool only provides aggregate district statistics, lacking other likely operations such as listing districts, retrieving raw records, or comparing over time. This creates significant gaps for agents needing more detailed or varied real estate data.
Available Tools
1 toolget_district_aggregateARead-onlyInspect
Aggregate distress real estate statistics for a Czech okres (district) from public registries (ISIR insolvencies + portál dražeb / CEVD forced sales). Returns counts by category (insolvency / auction) and average market data. To avoid identifying an individual, districts with 1–4 distress leads return null counts plus counts_band="<5" (records exist, exact figure withheld); 0 is shown as 0, ≥5 exact. low_activity flags k<5. Free tier — no per-person PII (no names/addresses).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| okres | Yes | Czech okres name (e.g. "Praha", "Brno-město", "Beroun"). Case-sensitive. | |
| window_days | No | Lookback window in days. Default 90. |
Tool Definition Quality
A4.5/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description gives substantial behavioral detail beyond the readOnlyHint annotation: suppression for 1–4 leads (null counts plus counts_band='<5'), the 0 and ≥5 thresholds, low_activity flag, and free tier. It also clarifies privacy guarantees (no names/addresses). This is far more than annotations alone.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences with dense, purposeful content: purpose, privacy suppression rules, and pricing/PII guarantee. Every sentence earns its place with no filler or redundancy.
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?
Given the tool's complexity (privacy suppression, thresholds, low_activity flag) and lack of an output schema, the description covers all essential behavioral nuances. An agent can accurately interpret returned counts and bands without additional documentation.
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?
The schema already provides 100% coverage of both parameters, including examples, defaults, enums, and case-sensitivity for okres. The description adds no parameter-specific semantics beyond the schema, so the baseline 3 is correct.
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?
The description opens with a specific verb ('Aggregate') and resource ('distress real estate statistics for a Czech okres'), and names the data sources (ISIR insolvencies + portál dražeb / CEVD). This clearly distinguishes it from any individual-level lookup, even though no sibling tools are provided.
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?
The description provides clear context: it is for district-level aggregate statistics from public registries, and explicitly notes that no per-person PII is included, implying it is not for individual-level searches. However, it does not explicitly mention alternatives or when-not-to-use scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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!
Related MCP Servers
- Flicense-qualityFmaintenanceFrench real estate data platform for AI agents. Identifies property owners likely to sell and tracks behavioral signals on active listings. Coverage: metropolitan France.
- AlicenseAqualityAmaintenanceUK property area intelligence: validated trajectory scores, gentrification early-warning and area screening for 2,292 England & Wales postcode districts, from 30+ government data sources.127MIT
- AlicenseAqualityDmaintenanceFrench building permits MCP server: 1.2M Sitadel permits (2014-2026, daily refresh), DVF transactions, cadastre DGFiP, PLU zoning, BRGM risks, and property-dealer opportunity scoring through 11 MCP tools. Free tier 500 req/month, no credit card.113MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.