booli-mcp

Search Booli sold listings (slutpriser)

booli_search_sold

Read-onlyIdempotent

Search sold Swedish properties on Booli to find comparables, including final sold prices and over/under-asking percentages, filtered by location, date, price, rooms, area, and type.

Instructions

Search sold properties (slutpriser) on booli.se with the achieved final price and over/under-asking % — the comparables for valuation. Scope by area_id or free-text location, filter by sold price, sold date, rooms, area, object type. Paginated by page. 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

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the description's 'Read-only' adds nothing new. It does contribute the result content (final price plus over/under-asking %) and pagination behaviour, but says nothing about external-API rate limits, auth, or completeness guarantees for an open-world scraping-style source.

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?

Front-loaded with the resource and its differentiating output, followed by scoping, filtering, pagination and the read-only note in short clauses. Slightly comma-dense in the middle sentence, but every clause carries information.

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, no-output-schema search tool, the description covers purpose, scope selection, filter categories, pagination and the two headline return metrics, leaving the detailed field semantics to an 82%-covered schema. It omits auth/rate-limit context for an external source, which is the only meaningful gap.

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 documents area_id vs location precedence, date formats, units (SEK, m²) and sort/view defaults. The description only groups filter categories at a high level (price, date, rooms, area, object type) and adds no semantics beyond the schema — the baseline 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?

States a specific verb and resource — searching sold properties (slutpriser) — and names the distinguishing output (achieved final price and over/under-asking %), which cleanly separates it from the active-listing sibling. The phrase 'the comparables for valuation' also tells the agent what this data is for.

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

Usage Guidelines3/5

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

The description implies the use case (valuation comparables) and lists scoping/filter options, but never names or excludes alternatives such as booli_search_listings (active listings) or booli_market_stats. An agent must infer from the word 'sold' that this is the right tool rather than being routed explicitly.

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

Deploy Server

Search Booli sold listings (slutpriser)

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools