City24.ee - Real Estate marketplace
Server Details
Live Estonia real estate listings with search, geo filters, and property metadata.
- 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 3.8/5 across 1 of 1 tools scored.
Only one tool exists, so there is no risk of confusion between tools.
The sole tool 'search-listings' follows a clear verb_noun naming pattern, consistent and descriptive.
A single tool for a real estate marketplace is too few; users would typically need multiple tools for CRUD, favorites, etc.
Only a search tool is provided, missing essential operations like creating, updating, or deleting listings, making the surface severely incomplete.
Available Tools
1 toolsearch-listingsAInspect
Search real estate listings by property type, transaction type, price range, area, floor, lot size, and location. Use locationName for the most specific known location (e.g., street, district, or city). Some filters apply only to certain property types: floor filters are for apartments, and lot area filters are for houses or land.
| Name | Required | Description | Default |
|---|---|---|---|
| areaMax | No | Maximum area in square meters | |
| areaMin | No | Minimum area in square meters | |
| floorMax | No | Maximum floor | |
| floorMin | No | Minimum floor | |
| priceMax | No | Maximum price | |
| priceMin | No | Minimum price | |
| unitType | Yes | The type of property | |
| roomCount | No | Number of rooms | |
| lotAreaMax | No | Maximum lot area in square meters | |
| lotAreaMin | No | Minimum lot area in square meters | |
| projectType | No | Building/project type (series) | |
| locationName | No | Target location at the lowest available level (e.g., street, district, or city) | |
| transactionType | Yes | The type of transaction |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that floor and lot area filters are property-type specific, but does not state that the operation is read-only, discuss authentication, rate limits, or behavior when no results are found.
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 concise, front-loaded with the main action, and every sentence adds meaningful guidance. No wasted words.
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 13 parameters and lack of output schema, the description covers overall purpose and key conditional rules, but omits details like pagination, result limits, search semantics (exact vs fuzzy), or ordering. It is adequate but not fully comprehensive for a search tool.
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%, baseline 3. The description adds value by explaining the intended use of locationName (most specific known location) and clarifying which filters apply to which property types, exceeding the schema's individual parameter descriptions.
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 it searches real estate listings and lists key filterable fields (property type, transaction type, price, area, floor, lot size, location). It is specific and informative, though no sibling tools exist to differentiate from.
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 advises using locationName for the most specific known location and notes that floor and lot area filters are conditional on property type. This provides clear usage context, though it does not mention when not to use the tool.
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!