Driverless delivery.
Scored across 11 tools
Each tool targets a distinct resource and action: booking vs cancelling vs tracking, and coverage checks vs store discovery vs owned-store listing are cleanly separated. find_stores (network-wide open stores) and list_stores (organization's own stores) are explicitly differentiated in their descriptions.
Almost all tools follow a consistent verb_noun snake_case pattern (book_delivery, cancel_delivery, register_store, update_store). The lone exception is wallet_balance, which drops the verb, a minor deviation.
11 tools is well-scoped for a delivery-plus-store-management domain, with each tool covering a genuine capability. No redundant or filler tools are present.
Strong lifecycle coverage: store registration/listing/update, coverage checks, full delivery flow (book, cancel, track, proof), and wallet operations. Minor gaps like a dedicated store deletion or account management operation exist, but agents can work around them.
Book a $2.99 robot delivery from a registered store in one call. Send store_id, dropoff_address and dropoff_phone; order_ref is the store's own order number (required at an open store); ready_at starts the 2-hour promise and defaults to now. The answer is yes or no now: a decline carries retry_after_seconds and a capacity.available webhook follows when capacity frees. A live key holds the posted price from the organization's Wallet; a test key creates a simulated robot delivery.
Inputs: dropoff_phone (required), dropoff_address (required), idempotency_key (required), parcel, +10 more.
Cancel before pickup; a successful cancellation releases the full fee hold. The owner of an open store may use this on another account's booking inside the decline window: that records store.declined and cancels with cancel_reason store_declined. After pickup the call returns not_cancellable. Safe to retry.
Inputs: delivery_id (required), robomart_version.
Can this store deliver to this address at this ready time? Send store_id (a registered store) and dropoff_address; ready_at defaults to now. Checks the store's status, hours and coverage radius, the 5-mile network maximum and the zone, and returns the $2.99 fee and the arrival window. Capacity is answered at booking.
Inputs: dropoff_address (required), parcel, ready_at, store_id, +2 more.
Live open stores near a drop-off address, nearest first, with whether each one's coverage radius reaches the address. Any account may book from an open store with an order_ref the store recognizes.
Inputs: address (required), limit, radius_miles, robomart_version.
Proof of a delivered Delivery, with its store_id and order_ref. Sandbox proof is explicitly marked simulated.
Inputs: delivery_id (required), robomart_version.
Stores this organization owns, with status, visibility, radius and activation. Use the store id to check coverage and book. Filter by status or visibility; page with starting_after.
Inputs: limit, status, visibility, starting_after, +1 more.
Register a store: a real place whose owner promises to load the robot. Send the name, the address, at least one alert channel the store owns (relay, webhook, sms or voice), and optionally where the robot parks (robot_spot), hours inside 10:00 to 22:00, the coverage radius (default 2 miles, maximum 5), private or open visibility, loading notes and your own external_ref. The store starts pending; the activation check makes it live.
Inputs: name (required), address (required), alert_channels (required), hours, +7 more.
Ask for a Wallet top-up of amount_credited cents (2000 to 1000000). The reply carries a signed confirmation link that a person completes in Console; no money moves until they do, and the link expires after 24 hours. Track it with GET /v1/topups/request/{id}.
Inputs: amount_credited (required), note, robomart_version.
The current Delivery, including store_id, store_name, order_ref, ready_at, promised_by and the pickup and return timestamps. Test deliveries are simulated.
Inputs: delivery_id (required), robomart_version.
Change a store you own: name, address, robot spot, hours, radius, visibility, alert channels, loading notes, perishables setting or external_ref; status pauses (paused) and resumes (live) a store. A pending store becomes live only through the activation check. Changing a live store's address or robot spot returns it to pending.
Inputs: store_id (required), name, hours, status, +9 more.
The Wallet balance for this organization and environment: available, held, this month's spend and the auto top-up setting. Reading only.
Inputs: robomart_version.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Agentic-AI route optimization for delivery fleets, capacity- and time-window-safe.
AI dispatch for food & local delivery: assigns orders to drivers, sequences stops, times departures.
Where you can ride a robotaxi today, city by city.
Add one secure layer between your agents and this server.
