No user-submitted related servers found.
Scored across 12 tools
Most tools have distinct targets, and the generic get_city_resource is clearly positioned as the fallback for many resource types. Intentional overlap exists between get_city/get_city_overview and air_quality vs resource='air', but the descriptions explicitly route agents to the correct tool. Station board and transit departures are also disambiguated by mode and ID type.
Names are readable and consistently snake_case, but the style is mixed: get_city/get_city_resource use verb_noun, while air_quality/weather/pois/sources are bare nouns and station_board_departures/transit_departures use noun_noun patterns. No single clear convention exists, though the get_city_* family provides some structure.
12 tools is well within the ideal range and each one supports a distinct workflow: discovery, single-city lookup, resource-specific retrieval, station boards, and multi-city comparison. No redundant tools stand out, and the generic resource accessor keeps the count from ballooning despite a large underlying data catalog.
The server covers the full read-only data lifecycle: list_cities for discovery, get_city_overview for a one-call catalog, get_city_resource for any of the 67 data types, convenience tools for common slices, and compare for multi-city analysis. For its stated purpose, there are no critical dead ends.