Lalamove MCP by usefulapi

Most tools target a distinct resource+action pair (quotation pricing, order placement, cancellation, driver replacement, priority fee). The one blurry boundary is lalamove_get_order vs lalamove_track_order, which both return status, stop proof of delivery and a share link, and lalamove_get_driver overlaps with the driver details embedded in track_order. The descriptions do differentiate them (track_order adds live driver coordinates for in-flight orders; get_order is the full record including price breakdown), so an agent can recover, but the split is not immediately obvious.

Every tool uses the same lalamove_ prefix followed by a clear verb_noun snake_case pattern (create_quotation, place_order, cancel_order, change_driver, list_cities, add_priority_fee). No camelCase or style mixing anywhere in the set.

Ten tools is well within the sweet spot and each maps to a real lifecycle step: discover cities/vehicles, price, order, inspect, track, cancel, adjust driver/tip. No tool feels like filler or a redundant alias.

The full delivery lifecycle is covered end to end: list_cities -> create_quotation -> place_order -> get_order/track_order -> get_driver/change_driver -> cancel_order, plus add_priority_fee. The one gap is discovery: there is no way to list or search past/active orders, so an agent needs an orderId from elsewhere to use the get/track/modify tools. That is largely a limitation of the underlying Lalamove API rather than a design flaw.