Skip to main content
Glama
chrischall

booli-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get a Booli property

booli_get_listing
Read-onlyIdempotent

Retrieve full details for any Swedish property by its Booli residence ID, covering active and sold listings, with compact or full response options.

Instructions

Full detail for one property by its Booli residence id — the number in a booli.se/bostad/ URL, or the residence_id from a search result. Works for both active and sold properties. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoResponse 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.
residence_idYesThe property's residence id (e.g. "4370936" from /bostad/4370936).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.1
    • removedInput schema / properties / compact
      Removed value: -{
-  "description": "Return a slim summary instead of the full raw record (default false).",
-  "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"
+}
  2. Changed3 schema fields changedv1.0.0
    • removedInput schema / properties / booli_id
      Removed value: -{
-  "description": "The listing's Booli id (e.g. \"1579812\").",
-  "type": "string"
-}
    • addedInput schema / properties / residence_id
      Added value: +{
+  "description": "The property's residence id (e.g. \"4370936\" from /bostad/4370936).",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "booli_id"
-]New value: +[
+  "residence_id"
+]
  3. First observedv0.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark readOnlyHint, idempotentHint, and openWorldHint; the description independently states 'Read-only' and adds useful scope by saying it works for both active and sold properties. It does not discuss rate limits or output size, but for a simple read operation the combination is sufficient.

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?

Two compact sentences with the primary action and identifier format front-loaded. The read-only qualifier is a single closing phrase, and 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?

This is a simple two-parameter read-only tool with strong annotations and full schema coverage, so little else is required. It could have explicitly named the search siblings as the way to find a residence_id when one is not already known, but the description already references search results as a source.

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

Parameters4/5

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

The schema covers 100% of parameters with detailed descriptions, so the baseline is 3; the description adds the operational hint that residence_id can be sourced from a booli.se URL or a search result's residence_id field. This helps the agent know where to obtain the required value beyond the schema's example.

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 'Full detail for one property by its Booli residence id', naming a specific verb, resource, and identifier format. It clearly separates this from the search siblings by focusing on single-property lookup and explicitly notes it covers active and sold properties.

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 tells the agent when to call the tool: when a residence id is already known, either from a booli.se/bostad/<id> URL or from a search result's residence_id field. It does not explicitly name alternative tools, but the by-id framing makes the contrast with search tools clear.

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

Deploy Server

Other Tools