No user-submitted related servers found.
Scored across 10 tools
Each tool targets a distinct resource and action: find_sailings searches, get_booking/list_bookings read, track_shipment follows movements, propose_* creates different plan types, and apply_plan/discard_plan manage plan lifecycle. There is no meaningful overlap between read, write, and lifecycle operations.
All tool names follow a consistent verb_noun snake_case pattern with specific, descriptive verbs. The naming convention is uniform across search, retrieval, planning, and application actions.
Ten tools is well-scoped for a booking and shipment management domain. Each tool represents a distinct workflow stage without redundancy or unnecessary bloat.
The set covers the core lifecycle: search sailings, propose and apply bookings, view bookings, track shipments, propose changes/cancellations, and discard plans. Minor gaps exist, such as no dedicated get-plan-by-id tool and no explicit refusal-handling action, but the existing tools appear sufficient for normal agent workflows.