overture-maps

overture_resolve_id

Read-onlyIdempotent

Resolve an Overture UUID without knowing its theme or position by querying the current GERS registry. Returns live feature, removed ID metadata, or not_in_registry status.

Instructions

Resolve a UUID without knowing its theme or position using the current GERS registry.

    Returns live feature and verified file, removed ID metadata, or not_in_registry.
    Registry is unversioned and excludes Addresses/Base/building_part. For those IDs or
    historical releases use overture_get_feature with known bounds. Never infer global
    nonexistence from not_in_registry. Default returns all properties and geometry.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fields`	No
`identifier`	Yes
`include_geometry`	No

Output Schema

TableJSON Schema

Name	Required	Default
`data`	Yes
`scope`	No
`theme`	No
`source`	Yes
`license`	Yes
`release`	Yes
`warnings`	No
`next_cursor`	No
`feature_type`	No
`attribution_url`	No	https://docs.overturemaps.org/attribution/

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 4, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, open world), and the description adds substantial non-obvious behavior: the registry is unversioned, excludes certain themes, and returns one of three states (live feature/verified file, removed metadata, not_in_registry). This is meaningful context the annotations cannot convey.

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 core purpose, then layers return states, exclusions, alternatives, and a caveat. Dense but each sentence carries distinct information; minor verbosity in the multi-clause return-state sentence.

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 enumerated, yet the description still maps the three outcome states usefully. It covers registry scope, alternatives, and interpretation caveats; the only residual gap is parameter-level detail for fields.

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 0% across three parameters, so the description must compensate. It does clarify the default (all properties and geometry), which maps to include_geometry and fields, but never explains the semantics of the fields list itself or identifier format. Partial compensation only.

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 (resolve) plus resource (a UUID/ID) and names the mechanism (current GERS registry) and the key differentiator: resolution without knowing theme or position. It is immediately distinguishable from overture_get_feature, which it explicitly references.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use overture_get_feature with known bounds for excluded IDs (Addresses/Base/building_part) or historical releases. It also warns never to infer global nonexistence from a not_in_registry result, which is exactly the kind of when-not-to-conclude guidance agents need.

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

Deploy Server