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
- 2
- 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.2/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of ambiguity or confusion between tools.
With a single tool, the naming pattern is inherently consistent; 'get_district_aggregate' follows a clear verb_noun structure.
The server covers a broad 'realestate' domain but exposes only one tool, which is too few for the apparent scope and results in a thin tool surface.
The single tool provides only aggregate district statistics for Czech real estate. All other potential real estate operations (listings, transactions, etc.) are missing, making the surface severely incomplete.
Available Tools
1 toolget_district_aggregateARead-onlyInspect
Aggregate distress real estate statistics for a Czech okres (district). Returns counts by category (insolvency / auction) and average market data. Low-volume districts are marked with low_activity. Free tier — no PII exposed.
| 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?
Annotations already declare readOnlyHint=true, so the description's main behavioral contribution is stating 'Free tier — no PII exposed' and noting the low_activity flag. While this adds value, it does not cover all behavioral aspects (e.g., no rate limits or auth requirements). The description is consistent with annotations and provides modest additional transparency.
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 three sentences long, with the main purpose in the first sentence. Every sentence adds unique information: aggregate function, return contents, and noteworthy constraints (low_activity, free tier, no PII). No fluff or repetition.
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?
Given the tool's simplicity (2 parameters, no output schema), the description adequately covers what the tool does and the nature of its output. It mentions counts by category, average market data, and the low_activity flag. However, it could be improved by describing the exact fields returned, but the current level is sufficient for an AI agent to understand the tool's purpose.
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 description coverage is 100% with detailed parameter descriptions (e.g., case-sensitive, examples, default value for window_days). The tool description adds minimal parameter-specific information beyond the schema, only mentioning 'Low-volume districts are marked with low_activity' which relates to output, not input params. Baseline 3 is appropriate as the schema already carries the burden.
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?
Description clearly states the verb 'Aggregate' and the resource 'distress real estate statistics for a Czech okres (district)'. It specifies what is returned (counts by category, average market data, low_activity flag) and includes additional context (free tier, no PII). With no sibling tools, differentiation is not needed, and the purpose is unambiguous.
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 the tool should be used for district-level aggregate statistics in the Czech Republic, but does not explicitly state when to use it or provide exclusions. Since there are no sibling tools, lack of explicit alternatives is acceptable. The description is clear enough for an AI agent to identify the correct context.
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.