CXT Software MCP by usefulapi

Tools are largely distinct: parallel order/route pairs (plan/optimize/save) are clearly separated by resource, and the two getters (cxt_get_dispatch_order vs cxt_get_order) are explicitly differentiated by login type. Minor risk remains between cxt_search_shipments, cxt_track_shipments and cxt_list_recent_orders, which all hit the same vendor endpoint and could be misselected if the description's criteria distinctions are skimmed.

All 14 tools use a consistent cxt_verb_noun snake_case pattern with predictable resource suffixes (_order_plan, _route_plan). Small deviations exist (singular/plural mix such as cxt_plan_orders vs cxt_optimize_order_plan, and cxt_get_dispatch_order vs cxt_list_recent_orders), but they stay readable and inferable.

14 tools is well within a healthy range and each earns its place: each corresponds to a distinct vendor endpoint with a clear role in the fetch/search/track/plan/commit lifecycle. No redundant or filler tools are present.

Core workflows are covered end to end: order retrieval in two views, recent list, search, tracking, planning limits, propose/optimize/commit for both orders and routes, and driver validation. Gaps exist (no order creation/cancellation, no driver listing, no update of order status outside planning), which agents cannot work around purely from this surface but which may be out of the API's scope.