Skip to main content
Glama
chrischall

booli-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Resolve a Booli area

booli_search_areas
Read-onlyIdempotent

Resolve a place name into Booli area IDs for municipalities, districts, and streets. Pass the returned area_id to search listings or sold properties.

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

A3.9/5.0
Behavior3/5

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

The annotations already cover safety with readOnlyHint, idempotentHint, and openWorldHint, lowering the bar. The description adds some behavioral context by specifying that it returns municipalities, districts, and streets each with an `area_id`, but 'Read-only' merely repeats what readOnlyHint already declares. It does not disclose ambiguity handling, multiple match behavior, or other runtime quirks.

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 core sentence is dense, front-loaded, and contains the essential purpose, output types, and downstream usage in one line. The trailing 'Read-only.' is redundant with the annotations but is harmless; the overall definition is compact and efficient.

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 simple two-parameter resolver with safe annotations, the description is largely complete: it explains the input, the output types, and how the output is consumed by sibling tools. Because there is no output schema, it would be slightly stronger to state what happens on no match or how many areas may be returned, but the essential calling context is present.

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 the schema already explains both `query` and `limit`. The description reinforces that `query` is a place name and that the result carries `area_id`, but it does not add meaningful parameter-level detail beyond what the input schema provides, so the baseline of 3 is appropriate.

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 uses a specific verb ('Resolve') plus a clear resource ('place name to Booli areas') and names the concrete output types: municipalities, districts, streets. It also differentiates the tool by stating that the resulting `area_id` feeds into booli_search_listings / booli_search_sold, so an agent can distinguish it from its siblings without opening their schemas.

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 gives clear context for when to use the tool: resolving a place name before searching listings or sold data via the returned `area_id`. It names the downstream tools, which implies the intended workflow, but it does not explicitly state when not to use this tool or name a direct alternative.

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