Live Estonia real estate listings with search, geo filters, and property metadata.
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.
Average 4.1/5 across 1 of 1 tools scored.
With only one tool available, there is no possibility of confusion or overlap. The single tool 'search-listings' clearly targets the search functionality.
The tool name follows a consistent verb_noun pattern ('search-listings'), and since there is only one tool, there are no conflicting conventions.
A single tool is too few for a real estate marketplace, which typically requires additional operations like retrieving listing details, creating listings, or contacting sellers. The server's scope seems broader than search alone.
The tool surface is severely incomplete for a marketplace. Only search is provided, with no way to view individual listing details, manage listings, or perform transactions, leaving agents unable to complete typical marketplace workflows.
search-listingsAInspectSearch 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 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses filter applicability constraints (floor filters for apartments, lot area for houses/land), which is valuable behavioral context. However, it does not mention return format, pagination, ordering, or error behavior—common details expected for a search tool. The description is moderately transparent but not comprehensive.
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 and front-loaded with the core purpose, followed by essential usage clarifications in just two sentences. Every sentence adds value, with no fluff or repetition of schema information.
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?
For a complex tool with 13 parameters and no output schema, the description provides good context on parameter usage and filter constraints. However, it lacks any mention of what the search returns (structure, pagination, sorting), which would be helpful given no output schema exists. It is adequate but leaves some gaps.
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%, so the baseline is 3. The description adds valuable semantic context beyond the schema: the locationName hierarchy (street, district, city) and the conditional applicability of floor/lot area filters. This enhances understanding of how to use the parameters correctly.
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's purpose: 'Search real estate listings' with specific filter dimensions (property type, transaction type, price range, area, floor, lot size, location). The verb 'search' and resource 'listings' are explicit, and the tool is well-distinguished by the detailed list of search criteria.
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?
While there are no sibling tools to differentiate from, the description provides practical usage guidance: using locationName for the most specific location, and clarifying that floor filters apply only to apartments and lot area filters only to houses/land. This gives clear context on how to use the tool correctly, though it doesn't explicitly state when not to use it.
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.
No comments yet. Be the first to start the discussion!
