Skip to main content
Glama
chrischall

booli-mcp

by chrischall

Search Booli for-sale listings

booli_search_listings
Read-only

Search active for-sale property listings by area, price, rooms, living area, and other filters. Find homes matching your criteria.

Instructions

Search active for-sale property listings on booli.se. Scope by q / area_id (from booli_search_areas) / center+dim / bbox, and filter by price, rooms, living area, plot, object type, construction year. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text area search (e.g. "Nacka", "Södermalm"). One of q / area_id / center / bbox scopes the search.
dimNoRectangle size in metres "w,h" (e.g. "400,500"), used with `center`.
bboxNoBounding box "lat_lo,lng_lo,lat_hi,lng_hi" (SW then NE corner).
limitNoDefault 30, max 100.
centerNoCoordinate "lat,lng" (e.g. "59.34674,18.0603"); use with `dim`.
offsetNoPagination offset.
area_idNoBooli area id(s) from booli_search_areas, comma-separated for several (e.g. "76,16").
compactNoReturn slim summary records (default true). Set false for full raw fields.
max_rentNoSEK/month
max_roomsNo
min_roomsNo
object_typeNoProperty type(s), comma-separated, from: villa, lägenhet, gård, tomt-mark, fritidshus, parhus, radhus, kedjehus.
max_plot_areaNo
min_plot_areaNo
max_list_priceNoSEK
min_list_priceNoSEK
max_living_areaNo
min_living_areaNo
max_list_sqm_priceNoSEK/m²
min_list_sqm_priceNoSEK/m²
is_new_constructionNotrue = only new production; false = exclude new production.
max_construction_yearNo
min_construction_yearNo
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true. Description adds 'Read-only', which is consistent but does not provide additional behavioral context beyond annotations. No mention of rate limits, authentication, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is a single sentence that efficiently conveys purpose, scoping, and filters. No wasted words, but could be slightly more structured (e.g., separate scoping and filtering).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with 23 parameters and no output schema, the description covers the core functionality well. It addresses scoping and filtering, but pagination (limit, offset) is not mentioned, though present in schema. Overall sufficient for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 83% with detailed descriptions for most parameters. Description mentions parameter categories but does not add meaningful semantics beyond the schema. Baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Search active for-sale property listings on booli.se' with specific verb and resource. Distinguishes from siblings like booli_get_listing and booli_search_sold by specifying 'active for-sale'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Describes how to scope the search (q, area_id, center+dim, bbox) and lists filter options. Implicitly distinguishes from sibling tools by focusing on active for-sale listings, but does not explicitly state when to use alternatives like booli_search_sold.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chrischall/booli-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server