booli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOOLI_API_KEY | Yes | Your Booli API key. | |
| BOOLI_CALLER_ID | Yes | Your Booli caller ID. |
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 |
|---|---|
| booli_search_areasA | Resolve a place name to Booli areas — municipalities, districts, streets — each with its |
| booli_search_listingsA | Search active for-sale property listings on booli.se. Scope by |
| booli_get_listingA | Full detail for one property by its Booli residence id — the number in a booli.se/bostad/ URL, or the |
| booli_search_soldA | Search sold properties (slutpriser) on booli.se with the achieved final price and over/under-asking % — the comparables for valuation. Scope by |
| booli_market_statsA | Aggregate sold-price statistics (median/average final price, price per m², average over/under-asking %) for an area on booli.se. Takes the same scope and filters as booli_search_sold, over one page of sold results. Check |
| booli_healthcheckA | Round-trips a small public www.booli.se URL (/graphql) through ContextMint Bridge (your signed-in browser tab) and returns diagnostics: the bridge's role (host/peer/null), port, version, the extension link (linked / pair pending / not attached / never answered), the elapsed round-trip time, and a plain-English hint distinguishing 'bridge never came up' from 'extension not connected' from 'this browser can't serve a capability' from 'real www.booli.se-side problem'. Read-only, no auth required. Call this when a real tool fails and you want to know which hop broke. |
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 6 tools
Each tool has a distinct role: diagnostics (healthcheck), ID lookup (get_listing), area resolution (search_areas), active search (search_listings), sold search (search_sold), and aggregates (market_stats). The sold-search vs market-stats boundary could be adjacent, but descriptions explicitly clarify that one returns listings and the other returns aggregate statistics.
All tools use a predictable booli_ prefix and snake_case. Most follow a verb_noun pattern (get_listing, search_areas, search_listings, search_sold), with minor deviations like healthcheck and market_stats that are still readable and idiomatic.
Six tools is well-scoped for a read-only property data API: one diagnostic, one area resolver, two search endpoints, one detail endpoint, and one aggregate stats endpoint. Each earns its place without redundancy.
The surface covers the core read-only lifecycle: area lookup, active/sold search, listing detail, and market aggregates. Minor gaps exist (e.g., no bulk listing fetch or comparable-listing helper), but agents can work around them by composing existing tools.