City24.lv - Real Estate marketplace
Server Details
Live Latvia 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 4.1/5 across 1 of 1 tools scored.
With only one tool, there is no possibility for confusion or overlap. The single tool's purpose is clear and unambiguous.
A single tool name 'search-listings' follows a clear verb_noun pattern (snake_case). There are no other tools to create inconsistency.
One tool for a real estate marketplace is too few. While the server may be intended only for search, the scope implied by the name suggests additional operations (e.g., get listing details, manage favorites) would be expected, making this count insufficient.
The server offers only a search tool, lacking any way to retrieve full details of a specific listing, manage listings, or perform other typical marketplace actions. This is a significant gap for the stated domain.
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 provided. Description implies read-only operation ('Search') and adds behavioral nuance by specifying that floor filters apply only to apartments and lot area filters to houses/land. This adds value beyond schema but lacks explicit safety or rate limit info.
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?
Three sentences, front-loaded with purpose, followed by actionable guidance. Every 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?
Covers all parameters and provides contextual filter rules, but does not describe return format, pagination, or ordering. Since no output schema exists, description should have compensated more.
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 covers 100% parameters. Description adds extra meaning by advising to use locationName for most specific location and clarifying filter applicability per property type, which is not obvious from schema alone.
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 it searches real estate listings with specific filter criteria, including property type, transaction type, price range, area, floor, lot size, and location. Verb+resource pair is specific and 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?
Provides clear usage guidance on locationName parameter for most specific location and conditional applicability of floor and lot area filters. However, no explicit when-not-to-use or alternatives are mentioned, though no siblings exist.
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!