booli-mcp

Booli sold-price market statistics

booli_market_stats

Read-onlyIdempotent

Calculate median and average sold prices, price per m², and over/under-asking percentages for a Swedish area from one page of Booli sold listings, with filters and sample-size counts.

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, computed over ONE page of sold results (most recent first by default) — page/pages say which, and total_count is the whole matching set, not the sample. sample_size is the rows on the page; sold_price_count / price_per_sqm_count / price_change_count are the rows that fed each metric. Check them 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: soldDate — most recent sales first with ascending false).
`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 changedv2.1.3Sep 24, 2026

changedInput schema / properties / sort / description

Previous value: -"Sort key (default: newest published)."New value: +"Sort key (default: soldDate — most recent sales first with ascending false)."

changedInput schema / properties / sort / enum

Previous value: -[
-  "published",
-  "listPrice",
-  "listSqmPrice",
-  "rooms",
-  "livingArea",
-  "rent",
-  "plotArea"
-]New value: +[
+  "published",
+  "listPrice",
+  "listSqmPrice",
+  "rooms",
+  "livingArea",
+  "rent",
+  "plotArea",
+  "soldDate",
+  "soldPrice"
+]

Changed1 schema field changedv2.0.0Sep 18, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

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.1/5.0

Behavior4/5

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

Annotations already establish read-only/idempotent/open-world behavior, so the bar is lower, and the description adds real value: it discloses that metrics are computed over ONE page of results, distinguishes total_count from sample_size, and warns that thin per-metric counts undermine a median. Those sampling semantics are genuine behavioral context beyond the annotations, though auth/rate-limit traits are not addressed.

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?

The purpose is front-loaded and each sentence carries information (sample reliability, total vs. sample distinction). The mid-sentence em-dash construction mixing input and output field names makes it slightly dense to parse, but nothing is redundant.

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?

With no output schema and 22 parameters, the description does substantial work by naming the returned metric fields, the row counts behind each metric, and the total-vs-sample distinction — compensating for the missing return-value spec. Some filter semantics still lean entirely on the schema, but nothing critical to calling it correctly is absent.

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 high (82%), so the schema already documents most of the 22 parameters, setting the baseline at 3. The description adds only a little param-level meaning ('page'/'pages' say which page — though no 'pages' param exists), and the field names it explains (sample_size, sold_price_count) are outputs rather than inputs.

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?

States a precise verb and resource — 'Aggregate sold-price statistics (median/average final price, price per m², average over/under-asking %)' — and explicitly anchors it to a sibling ('Takes the same scope and filters as booli_search_sold'). An agent can distinguish this aggregation tool from the listing-returning booli_search_sold without opening either schema.

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?

Clearly frames the tool as the aggregate counterpart to booli_search_sold, so the choice between them is inferable (stats vs. raw listings). It lacks an explicit when-to-use/when-not statement or a named alternative for edge cases, keeping it just below the top tier.

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