No user-submitted related servers found.
Scored across 19 tools
Most tools target distinct resources (departures vs arrivals, status vs itinerary, three infomobility detail levels), but there is real overlap: autocompleta_stazione and cerca_stazione both search stations by prefix and differ mainly in output shape, and autocompleta_stazione_nts overlaps the former. The descriptions mitigate this somewhat by explicitly noting output differences, but an agent could still easily misselect.
All names are lowercase snake_case Italian, which is highly consistent. However the convention mixes verb-led forms (autocompleta_stazione, cerca_numero_treno, elenco_tratte_ferroviarie) with pure noun phrases (tabellone_partenze, stato_treno, meteo_stazioni), so the pattern is readable but not strictly uniform.
19 tools is on the heavy side but justified by the broad domain: station lookup, boards, train status/tracking, network segments, statistics, infomobility, weather, and localization. Each tool maps to a genuinely distinct API capability, so few feel redundant.
The surface is comprehensive for a read-only public rail-data service: station search/detail/region listing, real-time arrivals and departures, train status and itinerary, network segments and occupancy, plus infomobility and weather. No obvious lifecycle gaps given it is inherently read-only, though nothing covers tickets or personal/favorites data.