list_locationsList cities and neighborhoods that have active listings, with counts. Call this first if unsure how a location is spelled. / Градове и квартали с активни обяви.
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | Optional: a city (BG or transliterated) → returns its neighborhoods |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool read-only, idempotent, open-world, and non-destructive. The description adds useful behavioral context: it returns counts, only includes active listings, and can return neighborhoods when a city is provided.
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 short, front-loaded with the core action, and includes a practical usage tip. The Bulgarian sentence repeats the title and adds no unique information, but the overall structure is efficient.
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 tool with one optional parameter, no required fields, and no output schema, the description gives enough to call it correctly. It could detail the exact response shape more, but the behavior is simple and the usage hint covers the main failure mode.
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?
The schema already documents the only parameter fully ('Optional: a city (BG or transliterated) → returns its neighborhoods'), so schema coverage is 100%. The description reinforces the parameter behavior but doesn't add meaning beyond what the schema provides.
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 names a specific verb and resource: lists cities and neighborhoods that have active listings, with counts. It also gives a concrete purpose (spelling lookup) that distinguishes it from property search tools.
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 explicitly says 'Call this first if unsure how a location is spelled,' which gives clear context for when to use it. It doesn't mention when-not-to-use or alternatives, but the guidance is actionable and sufficient for a simple lookup tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct action: searching, viewing details, stats, locations, subscription polling/creation, and inquiries. check_new_matches and search_properties both return listings, but one is explicitly subscription-scoped, so there is no real ambiguity.
All tool names follow a consistent lower_snake_case verb-first pattern: check_, get_, list_, search_, send_, subscribe_to_. The style is predictable and easy to follow.
Seven tools is well-scoped for a real estate search and contact server. Each tool covers a distinct step in the user journey without redundancy.
The core workflow is covered: browse locations, search, view details, get price stats, contact the agency, and set/receive new-listing alerts. A minor gap is subscription management, such as unsubscribing or updating a saved search, but agents can work around it.