Related Servers

Most tools target clearly distinct data domains (park & rail, sharing, charging, traffic, geocoding, road classification). Minor overlap exists between road_find_sharing (proximity) and road_search_sharing (full-text), and between road_traffic_counters (live data) and road_counter_sites (metadata), but descriptions explicitly clarify each role. The aggregate tools road_mobility_snapshot and road_multimodal_plan are distinguished as snapshot vs. route planner.

All 15 tools use snake_case with a uniform 'road_' prefix, giving a strong predictable family. The internal pattern is slightly mixed, however: some are verb_noun (road_find_sharing, road_geocode_address) while others are noun_noun (road_traffic_situations, road_counter_sites, road_mobility_snapshot), but readability remains high.

15 tools is well within the ideal range and each earns its place across distinct sub-domains (park & rail, sharing, charging, traffic, geocoding, road classification, aggregation). No redundant filler tools are present, and the count matches the breadth of a national mobility data server.

The surface covers discovery, live status, geocoding (forward/reverse), road classification, aggregation, and multimodal planning, giving broad lifecycle coverage for a data-serving server. Minor gaps: no charger detail-by-ID beyond status counts, and no explicit booking/link tool, but agents can work around these.