No user-submitted related servers found.
Scored across 33 tools
The large cluster of search/geocode tools (resolve_location, get_place_info, smart_geocode, search_nearby_places, find_nearby_amenities, search_osm_elements, get_place_details) overlaps heavily, and validate_coordinates vs validate_osm_data is easy to confuse. Descriptions do provide explicit guidance (marking some as compatibility or preferred alternatives), which keeps boundaries workable but not clean.
Nearly all tools use snake_case with a recognizable verb_noun pattern (get_osm_node, preview_node_create, apply_osm_edit, search_nearby_places). A few (smart_geocode, match_track_selection) are slightly off-pattern but still readable and snake_case, so minor deviation only.
33 tools is heavy and includes several near-duplicate compatibility wrappers (get_place_info, find_nearby_amenities) that inflate the surface beyond the core read/edit workflow. The GPX track sub-workflow adds another sizable group, pushing well past a well-scoped size.
Coverage is broad: element reads (node/way/relation/area), changesets and history, preview+apply editing with verification, GPX track analysis and road edits, geocoding, validation, export and statistics. Deletion of OSM elements is not exposed and validation is split, but core read/edit lifecycle is largely complete.