No user-submitted related servers found.
Scored across 20 tools
The descriptions do exceptional work with explicit 'Do NOT use' cross-references, so most tools have distinct purposes. However, several pairs are genuinely easy to confuse on first read — check_autobahn_traffic vs check_road_status vs find_roadworks_ahead, and get_train_departures vs get_departures — which rely heavily on the prose to separate.
Names follow a consistent verb_noun pattern throughout (check_, find_, get_, describe_, watch_, stop_). The verb variety maps sensibly to the action (find for discovery, check for status), and there is no mixing of casing or arbitrary styles.
20 tools is on the heavy side but the domain is genuinely broad (traffic, fuel, EV, parking, geocoding, transit, weather, watches, rules), and each tool appears to earn its place. Slightly over what one agent can comfortably hold, but not padded.
Coverage is strong across mobility data sources, with CRUD-like lifecycle on watches and multi-modal lookups. The notable gap is route planning/directions (A-to-B routing), which is a core navigation need, though the server explicitly declares its non-offerings so agents can work around them.