No user-submitted related servers found.
Scored across 20 tools
Most tools have clearly distinct resource+action targets (list_rides vs ride_detail vs ride_order vs ride_route). The main overlap is among aggregate/period tools: ride_summary, account_month_amount, and recharge_month all return computed monetary/statistical data and could be confused, as could recharge_history vs recharge_month. Descriptions mitigate this reasonably well.
All names use snake_case, which is consistent, but the convention mixes verb-first (list_rides, prepare_stats, recommend_ridepass, open_stats) with noun-phrase forms (account_profile, current_ride, ride_summary, pass_catalogue). Readable, but no single predictable pattern.
20 tools is at the high end but justified by the breadth of the domain (account, rides, routes, passes, recharges, payments, stats jobs, city rules). Slightly heavy, with a small cluster of stats-job tools, but each earns its place.
Broad read coverage: list/detail/summary across rides, recharges, passes, payments, account, plus analytics and city rules. The surface is essentially read-only, so action operations (booking a ride, buying a pass, topping up) are absent, but this appears to be an intentional analytics/read scope.