Booli MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOOLI_GRAPHQL_URL | No | The Booli GraphQL endpoint URL | https://api.booli.se/graphql |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_propertiesC | Search for properties on Booli.se with comprehensive filtering options |
| search_locationsB | Search for location suggestions on Booli.se to find area IDs and names |
| get_property_detailsB | Retrieve comprehensive details for a specific property using its property ID |
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 3 tools
Each tool has a clearly distinct purpose: get_property_details retrieves details for a specific property ID, search_locations finds location suggestions, and search_properties searches properties with filters. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.
All tool names follow a consistent verb_noun pattern with snake_case: get_property_details, search_locations, and search_properties. This predictable naming scheme enhances readability and usability for agents.
With 3 tools, the server is well-scoped for a property search domain, but it feels slightly thin as it lacks update or delete operations. However, given the domain (search and retrieval), the count is reasonable and each tool earns its place.
The tools cover core search and retrieval workflows for properties and locations on Booli.se, with no dead ends. A minor gap exists in not providing update or delete capabilities, but these may not be applicable to the domain, and agents can work effectively with the available tools.