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
- 3
- 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.
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.7/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion with other tools.
With only one tool, naming consistency is not a concern; the single name follows a clear verb_noun pattern.
The single tool covers a very specific domain (district-level aggregate real estate distress data), which is appropriate for a focused, free-tier API. However, one tool is minimal.
The tool provides comprehensive aggregate statistics for the intended domain, but lacks any individual property or detail-level operations, which is by design due to PII restrictions.
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).
| 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
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses important behaviors: the privacy mechanism (hiding low counts with counts_band '<5'), handling of zero vs. exact counts, and the free tier with no PII. This adds substantial context beyond the readOnlyHint annotation, fully informing the agent of data limitations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is slightly verbose (three sentences, the last one long) but well-structured: first sentence gives purpose, second explains privacy, third reiterates free and no PII. It is front-loaded with the main action, and each sentence adds value without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite no output schema, the description fully explains what the tool returns: counts by category, average market data, and how low counts are represented (null + counts_band). This is sufficient for an agent to understand and use the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, but the description adds crucial semantic details: 'okres' is case-sensitive, 'window_days' has default 90 and enum values. It also explains how the response behaves for low counts, which is not in the schema. This significantly aids correct invocation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool aggregates distress real estate statistics for a Czech district using specific public registries (ISIR insolvencies, forced sales). The verb 'Aggregate' and resource 'distress real estate statistics' are specific, and it distinguishes itself by mentioning the sources and the privacy handling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage context: for obtaining aggregate stats on Czech districts, with case-sensitive input and configurable lookback. It lacks explicit when-not-to-use or alternatives, but since no siblings are provided, the guidance is adequate for understanding appropriate use cases.
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!
Your Connectors
Sign in to create a connector for this server.