No user-submitted related servers found.
Scored across 25 tools
Each tool targets a distinct resource and action, with explicit disambiguation between similar families such as add_transport_option (between destinations) versus add_getting_around_option (local mobility), and toggle_event versus delete_trip_item. Polymorphic tools like update_destination_option and select_destination_option use a kind argument but their descriptions clearly explain the boundaries.
The set overwhelmingly follows a predictable verb_noun snake_case pattern (list_trips, create_variant, add_accommodation_option, update_event). The only deviations are whoami and connector_info, which are informational tools rather than CRUD operations, so the convention is still easy to follow.
Twenty-five tools is on the high side, but the trip-planning domain has several nested resources (trips, variants, destinations, three option kinds, events, goals) that justify most tools. Some option-add tools could potentially be consolidated, but each still earns its place.
Core lifecycle coverage is strong: trips, variants, destinations, options, and events all have create/read/update/select/delete paths. Minor gaps remain, such as no direct delete_trip operation, no revoke for share links, and goals only supporting list/add without update or delete.