No user-submitted related servers found.
Scored across 3 tools
Each tool targets a clearly distinct concern: train departure search, city lookup, and API health probing. There is no overlap in inputs or outputs, and the fed relationship (cities → train search) is obvious from the descriptions.
All names share the `flixtrain_` prefix and mostly follow verb_noun (search_trains, search_cities). `flixtrain_health` drops the verb form, a minor deviation that is still unambiguous.
Three tools is on the thin side but each earns its place for a read-only search integration. Nothing extraneous, though a slightly richer surface (e.g. station/connection detail) would feel less minimal.
Discovery (cities), the core search, and a diagnostic health check form a coherent lifecycle for a search-only server. Gaps like no journey detail/price breakdown endpoint or deeper filtering exist, but agents can work around them with the search result payload.