No user-submitted related servers found.
Scored across 5 tools
Each tool has a recognizable role: location lookup, bus journey search, journey detail, aggregate price stats, and flight summary. The main soft overlap is between obilet_price_stats and obilet_search_bus_journeys, since both take route+date and prices already appear in journey results, and price_stats is bus-only while flight_summary also reports price ranges. Descriptions do clarify the distinction (aggregate vs. listings), so confusion is limited.
All five tools share the obilet_ prefix and snake_case, which makes the set predictable and easy to scan. The only inconsistency is verb style: search_locations and search_bus_journeys lead with a verb, while price_stats, journey_detail, and flight_summary are noun-first phrases. It is still readable but not a strict verb_noun pattern.
Five tools is well within a healthy range for a read-only travel search domain. Each tool covers a distinct step (resolve locations, list journeys, inspect a journey, aggregate prices, summarize flights) with no filler tools. Nothing feels padded or conspicuously missing at the count level.
The surface supports the core workflow: find location ids, search bus journeys, drill into a journey, get price statistics, and get a flight overview. Gaps exist but are documented—no individual flight listings (explicitly broken upstream in v1) and no booking/purchase or advanced filtering on bus results. Agents can work around these within the stated informational purpose.