Related Servers

Several tools overlap or are explicit aliases: find_near is a thin alias of find_places, from_to is a legacy alias of route, resolve_place_batch is actually a batch of place_details rather than resolve_place, and geocode/resolve_place, reverse_geocode/address_at, and admin_lookup/reverse_geocode share overlapping outputs. However, the descriptions are unusually detailed and cross-reference canonical forms, so an agent reading them can usually pick correctly.

Most names are descriptive lowercase snake_case and there are coherent families (_at suffix, geocode*, *_matrix, summarize_*), but the set mixes verb_noun (find_places, summarize_area), noun_at (buildings_at, land_use_at), single nouns (isochrone, route, preferences), and awkward aliases (from_to, find_near). No case mixing, but the overall pattern is not uniform.

42 tools is a heavy surface for any MCP server. The broad domain justifies much of the count, but several tools are aliases or convenience composites that could be consolidated (find_near, from_to, within_distance, ground_location), and there are multiple geocoding/resolution variants plus batch versions. Agents face a large, navigationally dense tool list.

The server covers an unusually complete geospatial surface: place search/details, forward/reverse geocoding with batches, routing, matrices, isochrones, multi-stop optimization, meeting points, corridor search, area summaries/comparisons/verdicts, changes over time, building/land/water/infrastructure themes, geometry ops, map rendering, elevation, and system tools. Minor gaps include no arbitrary-GeoJSON-polygon place search, no division-boundary retrieval, and no direct address-to-place lookup, but these are workaroundable or consistent with the 'answers, not data' design.