bbox-mcp-server

aggregate_overpass_h3

Read-onlyIdempotent

Runs Overpass queries and bins results into H3 hexagons to analyze spatial density, then plots top hotspots on a shareable verification map.

Instructions

Executes an Overpass query and bins the results into H3 hexagons at a specified resolution to analyze spatial density. Plots the top density hotspots on the shareable verification map.

Input Schema

Name	Required	Description
`bbox`	No	The bounding box geometry to parse.
`query`	Yes	The Overpass QL core query (e.g. `nwr["amenity"="cafe"]`).
`location`	No	A text location to search for (e.g. 'Seattle').
`resolution`	Yes	The H3 resolution level (0-15) for binning. Default is 8.
`radius_meters`	No	Optional search radius in metres around the location/bbox center.
`timeout_seconds`	No	Overpass server query timeout in seconds. Default is 25.
`use_area_boundary`	No	If true (default), uses exact OSM boundary polygon for named locations when available.

Output Schema

Name	Required	Description	Default
`complete`	Yes
`warnings`	Yes
`share_url`	Yes
`hex_counts`	Yes
`provenance`	Yes
`resolution`	Yes
`hex_geojson`	Yes
`osm_area_id`	No
`alternatives`	No
`matched_place`	No
`original_bbox`	Yes
`total_elements`	Yes
`active_hex_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.5.0Nov 4, 2026

addedInput schema / properties / radius_meters

Added value: +{
+  "description": "Optional search radius in metres around the location/bbox center.",
+  "type": "number"
+}

addedInput schema / properties / timeout_seconds

Added value: +{
+  "description": "Overpass server query timeout in seconds. Default is 25.",
+  "type": "number"
+}

addedInput schema / properties / use_area_boundary

Added value: +{
+  "description": "If true (default), uses exact OSM boundary polygon for named locations when available.",
+  "type": "boolean"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "active_hex_count": {
+      "type": "number"
+    },
+    "alternatives": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "complete": {
+      "type": "boolean"
+    },
+    "hex_counts": {
+      "type": "object"
+    },
+    "hex_geojson": {
+      "type": "object"
+    },
+    "matched_place": {
+      "type": "string"
+    },
+    "original_bbox": {
+      "properties": {
+        "lat1": {
+          "type": "number"
+        },
+        "lat2": {
+          "type": "number"
+        },
+        "lng1": {
+          "type": "number"
+        },
+        "lng2": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "lat1",
+        "lng1",
+        "lat2",
+        "lng2"
+      ],
+      "type": "object"
+    },
+    "osm_area_id": {
+      "type": "number"
+    },
+    "provenance": {
+      "properties": {
+        "attribution": {
+          "type": "string"
+        },
+        "cache_age_ms": {
+          "type": "number"
+        },
+        "cached": {
+          "type": "boolean"
+        },
+        "data_timestamp": {
+          "type": "string"
+        },
+        "provider": {
+          "type": "string"
+        },
+        "usage_policy": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "provider",
+        "data_timestamp",
+        "cached",
+        "cache_age_ms"
+      ],
+      "type": "object"
+    },
+    "resolution": {
+      "type": "number"
+    },
+    "share_url": {
+      "type": "string"
+    },
+    "total_elements": {
+      "type": "number"
+    },
+    "warnings": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "resolution",
+    "total_elements",
+    "active_hex_count",
+    "hex_counts",
+    "hex_geojson",
+    "original_bbox",
+    "share_url",
+    "provenance",
+    "complete",
+    "warnings"
+  ],
+  "type": "object"
+}

First observedv1.2.4Apr 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds that results are plotted onto a 'shareable verification map', which hints at a persistent side effect not captured by the annotations, but it says nothing about Overpass timeout behaviour, query failures, or how many hotspots are retained.

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 sentences, front-loaded with the core action (query + H3 binning) before the secondary output behaviour (hotspot plotting). No filler or redundant restatement of the name.

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?

An output schema exists, so return values need not be explained, and the oneOf location/bbox exclusivity is handled structurally by the schema. What remains thin is operational context around failure modes and the nature of the plotted map output, but overall the description is adequate for a seven-parameter read tool.

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 every parameter including query, resolution, bbox/location, radius_meters, timeout_seconds, and use_area_boundary is already documented in the schema. The description only echoes that resolution drives the binning and adds no format or default guidance beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names two concrete operations: executing an Overpass query and binning results into H3 hexagons at a resolution, plus plotting density hotspots. This is a specific verb+resource statement an agent can act on. It does not explicitly contrast with the sibling search_overpass or get_h3_indices, so differentiation is left implicit.

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?

Usage is only implied: the tool is for spatial density analysis rather than raw feature retrieval. There is no explicit statement of when to pick this over search_overpass (raw results) or get_h3_indices (index retrieval), and no prerequisites or exclusions are given.

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

Deploy Server