Skip to main content
Glama
chrischall

booli-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Resolve a Booli area

booli_search_areas
Read-onlyIdempotent

Resolve Swedish place names to Booli area IDs for municipalities, districts, or streets, then pass that area_id into listing and sold-price searches.

Instructions

Resolve a place name to Booli areas — municipalities, districts, streets — each with its area_id to pass as area_id into booli_search_listings / booli_search_sold. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 10).
queryYesPlace-name search string (e.g. "Nacka", "Södermalm").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed8 schema fields changedv1.0.0
    • removedInput schema / properties / lat
      Removed value: -{
-  "description": "Latitude; use together with `lng`.",
-  "type": "number"
-}
    • changedInput schema / properties / limit / description
      Previous value: -"Default 10, max 50."New value: +"Max results (default 10)."
    • removedInput schema / properties / lng
      Removed value: -{
-  "description": "Longitude; use together with `lat`.",
-  "type": "number"
-}
    • removedInput schema / properties / only_with_listings
      Removed value: -{
-  "description": "Only return areas that currently have listings for sale.",
-  "type": "boolean"
-}
    • removedInput schema / properties / only_with_sold
      Removed value: -{
-  "description": "Only return areas that have sold listings.",
-  "type": "boolean"
-}
    • removedInput schema / properties / q
      Removed value: -{
-  "description": "Place-name search string (e.g. \"Nacka\").",
-  "type": "string"
-}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Place-name search string (e.g. \"Nacka\", \"Södermalm\").",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "query"
+]
  3. First observedv0.0.0

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, idempotentHint=true, destructiveHint=false, so 'Read-only' in the description is largely redundant. However, with no output schema, the description adds real value by disclosing the return shape (each area carries an `area_id`), which is the key behavioral fact an agent needs.

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?

A single sentence, front-loaded with the verb and resource, then the downstream handoff, then a safety tag. Nothing is wasted and no clause is buried.

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 two-parameter lookup with no output schema, the description covers purpose, downstream use, and return shape, which is what an agent needs to call it correctly. Minor gaps remain (result ordering, ambiguity handling for multi-match place names), but nothing blocking.

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 100%, so both `query` and `limit` are already documented in the schema (including the default of 10). The description adds no syntax, format, or matching-semantics detail beyond the schema, so the baseline of 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 ('Resolve a place name to Booli areas') and enumerates the entity types returned (municipalities, districts, streets). It also names the sibling tools it feeds (booli_search_listings / booli_search_sold), so an agent can place it in the workflow without opening a 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?

The description makes the usage contract explicit: call this first to turn a place name into an `area_id`, then pass that id into booli_search_listings / booli_search_sold. It gives clear context but no explicit 'do not use this for X' exclusion (e.g. resolving non-place inputs).

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