Mapsource OpenStreetMap & Geospatial APIs

overpass_query

Execute bounded Overpass QL over OSM nodes, ways, relations, tags, geometry, areas, metadata, and spatial selectors. Historical attic queries are unsupported. Requires a subscription key or authorized x402 payment. Use service_status to retrieve the dataset timestamp.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	A complete bounded Overpass QL query, with explicit timeout and output limit.
`responseMode`	No	compact: inline when small, a result handle when large. handle: always a handle. raw: always the full body, however large.	compact

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 9, 2026

addedInput schema / properties / responseMode

Added value: +{
+  "default": "compact",
+  "description": "compact: inline when small, a result handle when large. handle: always a handle. raw: always the full body, however large.",
+  "enum": [
+    "compact",
+    "handle",
+    "raw"
+  ],
+  "type": "string"
+}

First observedSep 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose key traits: the query must be bounded, historical attic queries are rejected, auth is required (subscription key or x402 payment), and the dataset timestamp lives behind service_status. It omits rate limits, error semantics, and cost/credit implications of large queries.

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-loads the capability, then tacks on the exclusions, auth requirement, and cross-reference in three tight sentences with no filler. It is appropriately sized for a two-parameter tool, though slightly clipped at the end.

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 tool with no output schema and no annotations, it covers the essential call-time facts (bounded input, auth, unsupported query class, where to get dataset recency). It leaves the shape/size of the returned results only partially implied by the responseMode enum in the schema.

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 documents 'query' (bounded QL with explicit timeout and output limit) and 'responseMode' (compact/handle/raw). The description adds no syntax, format, or default details beyond that, so it meets the baseline but adds no marginal meaning.

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?

States a specific verb (Execute) and resource (bounded Overpass QL over OSM nodes/ways/relations/tags/geometry/areas), which makes the tool's nature clear. It doesn't explicitly contrast itself with nearby siblings like find_features or geo_search, so the agent must infer when raw QL is preferable.

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?

Provides concrete usage constraints: historical attic queries are unsupported, and a subscription key or authorized x402 payment is required. It also routes the agent to service_status for the dataset timestamp, but never states when to prefer this tool over find_features/geo_search for the same task.

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

All Mapsource OpenStreetMap & Geospatial APIs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?