ImotAI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IMOTAI_API_URL | No | Base URL of the ImotAI public API. Optional; defaults to https://imotai.bg/api. | https://imotai.bg/api |
| IMOTAI_HTTP_TIMEOUT_MS | No | Per-request timeout in milliseconds. Optional; defaults to 15000. | 15000 |
| IMOTAI_RATE_LIMIT_PER_MIN | No | Max downstream requests per minute (token bucket, per process). Optional; defaults to 60. | 60 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_districtsA | List the districts (neighbourhoods) of a Bulgarian city that ImotAI has data for, with the count of active listings in each where a public price page exists. Call this first to learn which "district" values are valid for the other ImotAI tools in a given city. |
| search_propertiesB | Search Bulgarian real-estate listings on imotai.bg by city, district, property type, price range, area range and rooms. Returns up to 25 listings with structured fields, a link to each, and a district-level marketContext block (district average price per m² and how far this listing deviates from it). No contact details or free-text descriptions. |
| get_propertyA | Get the full structured data for one ImotAI listing by its id or slug: price, price per m², area, rooms, floor, construction, heating, location (city/district), features, and an authoritative per-listing marketContext (district average and median price per m², deviation percent, comparable active count). Does NOT return the broker free-text description, contact details, or exact coordinates. |
| get_market_statsA | The market picture for a Bulgarian city or district on imotai.bg: number of offers, average and P25/P50/P75 for total price and price per m², a breakdown by room count, and the neighbouring districts for comparison. Sale offers, all residential types. Returns { available: false } below 8 offers. |
| estimate_valueA | Rough price positioning for a property by city, district, type and area — based on the CURRENT ASKING PRICES of comparable active listings, not on closed transactions. Returns an estimate, a low–high range, a confidence level from sample size, and a mandatory disclaimer. Refuses below 5 comparable offers. You MUST show the "disclaimer" field to the user verbatim whenever you cite any number from this tool. Never call this an official or precise property valuation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct action and resource: searching listings, retrieving one listing, getting district-level market aggregates, estimating a specific property's value, and listing valid districts. The descriptions explicitly clarify boundaries (e.g., market_stats vs. estimate_value differ in scope and output), so an agent can reliably choose the right tool.
All tool names use a consistent verb_noun snake_case pattern: get_property, get_market_stats, estimate_value, list_districts, search_properties. There are no mixed conventions or vague verbs.
Five tools is well-scoped for a read-only real-estate data server, covering search, detail, market context, estimation, and district lookup. Each tool clearly earns its place without redundancy.
The surface covers the core workflows: search, property detail, market statistics, valuation estimate, and district enumeration. Minor gaps exist, such as no tool to list valid cities (needed as input to other tools) and no pagination beyond 25 search results, but these are workable.