booli-mcp

Booli sold-price market statistics

booli_market_stats

Read-only

Aggregate sold-price statistics for a Swedish area: median/average final price, price per m², and over/under-asking percentage. Apply filters to narrow results; check sample size before trusting thin datasets.

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, over one page of sold results. Check sample_size before trusting a thin median. Read-only.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	1-based page (default 1).
`sort`	No	Sort key (default: newest published).
`view`	No	Response shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact returns the slim PropertySummary/detail projection; "full" returns Booli's whole GraphQL node.
`area_id`	No	Booli area id from booli_search_areas. Provide this OR `location`.
`location`	No	Free-text place name (e.g. "Nacka", "Södermalm") resolved to its top Booli area. Ignored when `area_id` is set.
`ascending`	No	Sort ascending (default false).
`max_rooms`	No
`min_rooms`	No
`object_type`	No	Property type(s), comma-separated, from: Lägenhet, Villa, Kedjehus-Parhus-Radhus, Fritidshus, Gård, Tomt/Mark.
`max_plot_area`	No	m²
`max_sold_date`	No	Latest sold date, YYYYMMDD.
`min_plot_area`	No	m²
`min_sold_date`	No	Earliest sold date, YYYYMMDD (e.g. "20240101").
`max_sold_price`	No	SEK
`min_sold_price`	No	SEK
`max_living_area`	No	m²
`min_living_area`	No	m²
`max_sold_sqm_price`	No	SEK/m²
`min_sold_sqm_price`	No	SEK/m²
`is_new_construction`	No	true = only new production; false = exclude new production.
`max_construction_year`	No
`min_construction_year`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.3.1Sep 10, 2026

removedInput schema / properties / compact

Removed value: -{
-  "description": "Return slim summary records (default true). Set false for full raw fields.",
-  "type": "boolean"
-}

addedInput schema / properties / view

Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact returns the slim PropertySummary/detail projection; \"full\" returns Booli's whole GraphQL node.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}

Changed13 schema fields changedv1.0.0Jul 14, 2026

changedInput schema / properties / area_id / description

Previous value: -"Booli area id(s) from booli_search_areas, comma-separated for several (e.g. \"76,16\")."New value: +"Booli area id from booli_search_areas. Provide this OR `location`."

addedInput schema / properties / ascending

Added value: +{
+  "description": "Sort ascending (default false).",
+  "type": "boolean"
+}

removedInput schema / properties / bbox

Removed value: -{
-  "description": "Bounding box \"lat_lo,lng_lo,lat_hi,lng_hi\" (SW then NE corner).",
-  "type": "string"
-}

removedInput schema / properties / center

Removed value: -{
-  "description": "Coordinate \"lat,lng\" (e.g. \"59.34674,18.0603\"); use with `dim`.",
-  "type": "string"
-}

removedInput schema / properties / dim

Removed value: -{
-  "description": "Rectangle size in metres \"w,h\" (e.g. \"400,500\"), used with `center`.",
-  "type": "string"
-}

removedInput schema / properties / limit

Removed value: -{
-  "description": "Default 30, max 100.",
-  "maximum": 100,
-  "minimum": 1,
-  "type": "integer"
-}

addedInput schema / properties / location

Added value: +{
+  "description": "Free-text place name (e.g. \"Nacka\", \"Södermalm\") resolved to its top Booli area. Ignored when `area_id` is set.",
+  "type": "string"
+}

removedInput schema / properties / max_rent

Removed value: -{
-  "description": "SEK/month",
-  "minimum": 0,
-  "type": "number"
-}

changedInput schema / properties / object_type / description

Previous value: -"Property type(s), comma-separated, from: villa, lägenhet, gård, tomt-mark, fritidshus, parhus, radhus, kedjehus."New value: +"Property type(s), comma-separated, from: Lägenhet, Villa, Kedjehus-Parhus-Radhus, Fritidshus, Gård, Tomt/Mark."

removedInput schema / properties / offset

Removed value: -{
-  "description": "Pagination offset.",
-  "maximum": 9007199254740991,
-  "minimum": 0,
-  "type": "integer"
-}

addedInput schema / properties / page

Added value: +{
+  "description": "1-based page (default 1).",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

removedInput schema / properties / q

Removed value: -{
-  "description": "Free-text area search (e.g. \"Nacka\", \"Södermalm\"). One of q / area_id / center / bbox scopes the search.",
-  "type": "string"
-}

addedInput schema / properties / sort

Added value: +{
+  "description": "Sort key (default: newest published).",
+  "enum": [
+    "published",
+    "listPrice",
+    "listSqmPrice",
+    "rooms",
+    "livingArea",
+    "rent",
+    "plotArea"
+  ],
+  "type": "string"
+}

First observedv0.0.0Jul 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only'. It adds behavioral nuance beyond annotations by warning to check `sample_size` before trusting a thin median and clarifying that aggregation happens over one page of sold results.

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?

Three sentences, no filler. The core purpose is front-loaded, the sibling relationship is stated in the second sentence, and the sample_size caveat is the final actionable warning. Every sentence earns its place.

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 22-parameter tool with no output schema, the description is surprisingly complete: it names the output metrics, ties filters to a known sibling, and flags a data-quality caveat. It does not spell out the area requirement, but the schema's area_id/location descriptions already cover that.

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 82%, so the schema already carries most parameter meaning. The description adds little parameter-level detail, though referencing booli_search_sold for scope and filters is useful shorthand. No contradiction or gap large enough to lower below the high-coverage baseline.

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 opens with a specific verb and resource: 'Aggregate sold-price statistics' and enumerates exactly what is returned (median/average final price, price per m², over/under-asking %). It clearly differentiates from siblings by framing this as an aggregate tool while booli_search_sold is the underlying per-result search.

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?

It explicitly ties usage to booli_search_sold: 'Takes the same scope and filters as booli_search_sold', which tells the agent when to reach for this tool instead of the search sibling. It also adds the important one-page limitation. It does not explicitly state when not to use it, but the context is strong enough to route correctly.

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

Deploy Server

Booli sold-price market statistics

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools