Skip to main content
Glama
chrischall

booli-mcp

by chrischall

Booli sold-price market statistics

booli_market_stats
Read-only

Aggregate sold-price statistics (median, average, price per m², over/under-asking %) for a Swedish area. Use same filters as sold search. Check sample_size before trusting median.

Instructions

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. Check sample_size before trusting a thin median. 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
max_sold_dateNoLatest sold date, YYYYMMDD.
min_plot_areaNo
min_sold_dateNoEarliest sold date, YYYYMMDD (e.g. "20240101").
max_sold_priceNoSEK
min_sold_priceNoSEK
max_living_areaNo
min_living_areaNo
max_sold_sqm_priceNoSEK/m²
min_sold_sqm_priceNoSEK/m²
is_new_constructionNotrue = only new production; false = exclude new production.
max_construction_yearNo
min_construction_yearNo
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description adds value by specifying the exact statistics computed and the sample_size check. It does not contradict annotations and provides additional behavioral context beyond what annotations convey.

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

Conciseness5/5

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

The description is two concise sentences plus 'Read-only.' It is front-loaded with the core purpose and provides essential caveats without unnecessary words.

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?

Given 25 parameters and no output schema, the description adequately covers the output (specific statistics) and a key usage note (sample_size). However, it does not describe the output structure, which could be helpful for an agent. Still, it provides sufficient context for the tool's purpose.

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 description coverage is 84% (high), so baseline is 3. The description does not elaborate on individual parameters, but it notes that the tool uses the same scope and filters as booli_search_sold, which indirectly clarifies parameter usage. No extra parameter-level detail is added.

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?

The description clearly states the tool aggregates sold-price statistics (median/average price, price/m², over/under-asking %) for an area, with a specific verb (aggregate) and resource (sold-price market statistics). It distinguishes from siblings by referencing the same scope and filters as booli_search_sold.

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?

The description implies when to use (when aggregated statistics are needed) and provides a caveat to check sample_size before trusting a thin median. It mentions booli_search_sold as a sibling with the same scope, suggesting an alternative for individual listings, but lacks explicit 'when not to use' guidance.

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