kira-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KIRA_CACHE_DIR | No | Directory where geocoding results are cached. | OS cache dir |
| KIRA_USER_AGENT | No | User agent used when making requests. | kira-mcp/<version> (+repo url) |
| KIRA_RON_PER_EUR | No | Exchange rate used to convert RON prices to EUR. | 5.0 |
| KIRA_REQUEST_DELAY | No | Seconds to wait between requests to the same site. | 1.2 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_rentalsA | Search apartments for rent in a Romanian locality, live, across storia.ro, publi24.ro and lajumate.ro. Returns de-duplicated listings with extracted facts (price in EUR, rooms, surface, heating type, parking) and links to the original ads, plus per-site status. |
| get_listing_detailsA | Full description, photos and extracted facts for one ad. Use it before recommending a listing: heating and parking are often only in the full text. |
| search_parkingB | Parking spots and garages for rent in a Romanian locality (storia.ro). |
| find_localityA | Which Romanian localities match a name (with county, type and population). Use it when a name is ambiguous — there are e.g. several 'Florești'. |
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 4 tools
Each tool has a clearly distinct purpose: rental search, single-listing details, parking search, and locality disambiguation. There is no meaningful overlap between searching rentals and searching parking, and get_listing_details is clearly a follow-up to search_rentals.
All tools follow a consistent snake_case verb_noun pattern: search_rentals, get_listing_details, search_parking, find_locality. The slight verb variation (search/get/find) is semantically natural and does not break the predictable structure.
Four tools is well-scoped for a focused rental-search server. Each tool earns its place by covering a distinct step in the workflow: locate the locality, search rentals, inspect details, and optionally search parking.
The core workflow is covered: find a locality, search rentals or parking, and inspect a listing in detail. Minor gaps exist, such as no explicit tool for comparing listings or retrieving listing status/contact information, but agents can work around these.