No user-submitted related servers found.
Scored across 16 tools
Most tools have clear, distinct roles: location lookup, route search/detail, seat availability, reference lists, and the account/ticket lifecycle are well separated. The one weak spot is the trio get_ticket / get_my_ticket / list_my_tickets, where the boundary between retrieving 'an existing ticket by account code' and 'one ticket of the logged-in account' requires careful reading of descriptions.
All names are snake_case verb_noun (get_ticket, search_routes, list_seat_classes, create_reservation, cancel_ticket), with consistent get_/list_/find_/search_/create_/cancel_/pay_ prefixes. Exceptions like pay_ticket_with_credit still fit the verb-first convention and remain readable.
16 tools is at the upper bound but justified by the domain: five cheap list_* reference lookups (tariffs, seat classes, vehicle standards, carriers, action prices) support the core search/book/pay flow. A couple of the list endpoints (carriers, vehicle standards) are marginally useful, so it is slightly over-scoped rather than well-scoped.
The booking lifecycle is well covered end-to-end: locate stations, search routes, inspect detail/seats, reserve, pay with credit, and cancel, plus account and ticket retrieval. The main gap is the absence of a modify/update-reservation operation, forcing users to cancel and recreate; there is also no explicit passenger-detail handling visible in the surface.