Skip to main content
Glama
koizumikento

overture-maps

by koizumikento
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OVERTURE_MAPS_MCP_STORAGE_DIRNoStorage directory used by the MCP server for its dedicated environment and caches (e.g. "$PWD/.runtime").

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
overture_catalogB

Discover all six themes/types and available releases. Pin a release for later calls.

Use before searching; does not query geographic features or resolve an address.

overture_schemaA

Inspect dataset columns for a theme/type before filtering or grouping.

    Use with a pair from overture_catalog; reads Parquet metadata, not feature rows.
overture_searchA

Search intersecting features in a bounded WGS84 area across any of the six themes.

    Name is literal case-insensitive substring; category is exact taxonomy.primary (places).
    Confidence is places-only. Invalid filters produce errors rather than being ignored.
    Pass next_cursor unchanged with the same explicit release/filters for the next page.
    Choose bounds, center/radius_m, or GeoJSON Polygon/MultiPolygon (holes supported).
    All properties are available; fields selects paths. filters combines up to 20 typed
    AND conditions, including nested/list paths (sources[].dataset). No user SQL.
    Distance order needs center; include_metrics returns whole-feature m² / line meters.
    geojson returns a paginated FeatureCollection; retain the response provenance.
overture_get_featureA

Get a UUID feature from search with its known bounding area and pinned release.

With bounds, lookup is pinned to that area/release. Without bounds, uses the current GERS registry and its verified shard, and requires the matching theme/type/current release. Non-GERS types and historical releases need bounds. Empty scoped results do not establish global nonexistence. fields chooses properties; default is all.

overture_summarizeA

Count all dataset features intersecting a bounded area, optionally group by a column.

    Accepts exactly the same area/attribute conditions as search. Group by up to 3 scalar
    property paths; top 50 groups with other_count. Aggregate sum/avg/min/max/count/
    count_distinct of properties or @area_m2/@length_m/@distance_m (needs center).
    Geometry metrics default to clipped scope; circles use a 128-segment clip polygon.
    Counts and property aggregates are over whole intersecting records, not prorated.
overture_nearestA

Find the nearest intersecting features within a maximum radius; distance in meters.

Searches points, lines and polygons; polygon containing center has zero distance. Stable order is distance then ID. Point distances are geodesic; line/polygon edges use a local azimuthal-equidistant projection. Empty means none within the radius.

overture_spatial_joinA

Relate features across themes/types in one release and bounded area.

    Relation is left-to-right: places within division_area, or areas containing places.
    Both datasets are scoped to bounds; <=5000 candidates each or fail without partial
    analysis. pairs paginates pairs with properties/provenance; count returns total pairs;
    group_left returns every left ID with match count, including zero. within_distance
    needs distance_m and uses a local projected minimum geometry distance in meters.
overture_compare_releasesA

Compare two available release snapshots by ID in the same area and filters.

    Returns exact added/removed/modified/unchanged counts and paginated changes, including
    before/after properties and schema changes. Compares all properties regardless of
    fields selection, plus topological geometry equality. <=5000 records per snapshot.
    Added/removed can mean crossing scope/filters; not global creation/deletion. IDs in
    Addresses/Base/building_part lack GERS stability. Use catalog for available releases.
overture_resolve_idA

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

A3.9/5.0

Scored across 9 tools

Disambiguation4/5

Most tools have clearly distinct purposes (catalog vs schema vs summarize vs spatial_join vs compare_releases). However, overture_get_feature and overture_resolve_id both retrieve a feature by UUID, and overture_search vs overture_nearest both find intersecting features, so a couple of boundaries rely on descriptions rather than being inherently separate.

Naming Consistency4/5

All tools share a consistent overture_ snake_case prefix with predictable verb/verb_noun forms (search, get_feature, summarize, spatial_join, compare_releases, resolve_id). Minor deviation: catalog and schema are noun-style rather than action verbs, but the overall pattern is readable and uniform.

Tool Count5/5

Nine tools is well-scoped for a rich geospatial dataset, with each tool covering a distinct capability (discovery, schema, search, nearest, retrieval, aggregation, joins, release diffing). No redundant or filler tools.

Completeness5/5

The surface covers the full read-only query lifecycle: theme/release discovery, schema inspection, spatial and attribute search, distance search, feature retrieval, aggregation, cross-theme joins, release comparison, and ID resolution. No obvious gaps remain for a read-only dataset domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources