Loading ToolBench
Bold Commerce MCP server presents a well-curated, focused set of 11 ecommerce checkout tools with strong domain specificity. Tools are intentionally designed for AP2 payment processing workflows with clear, detailed descriptions and typed input schemas. Schema quality is high with required fields, nested object structures, and descriptive field-level documentation. However, incomplete descriptions (tools 1, 2, 8 truncate mid-sentence) and generic empty object schemas (tools 1, 9) reduce perfect execution. This is NOT auto-generated from a generic API spec, tools are business-logic aware with context-specific requirements (AP2 mandate handling, shop selection, intelligent order diffing).
For AP2 implementations using a mock payment provider, returns content to attach to the PaymentMandate in a subsequent process-order tool call. Only call this tool when using AP2 and only when using the mock payment provider. Call this tool immediately prior to processing the order, but only after signing the cart mandate.
For AP2 implementations, signs the 'CartMandate' such that callers know that the order is guaranteed to match expectations. Only call this tool when using AP2. Call this tool after the order is created, and prior to processing the order. Call this tool again after any change to the order before presenting to the user for confirmation.
Cancels an existing checkout session. Maps to POST /checkouts/:id/cancel endpoint.
Creates a new checkout session with items, buyer information, and shipping address. Maps to POST /checkouts endpoint.
Retrieves an existing checkout session by ID. Maps to GET /checkouts/:id endpoint.
Processes a checkout session with payment data. Tokenizes payment via EPS and processes the order (sets is_processed, queues pipeline jobs). Maps to POST /checkouts/:id/process_order.
Incomplete truncated descriptions on ap2-get-mock-payment-data, ap2-sign-cart, and select-shop, mid-sentence cutoffs suggest documentation retrieval or payload size issues
Generic empty object schemas on ap2-get-mock-payment-data and server-status provide no guidance for tool invocation, agents cannot determine required vs. optional parameters
ap2-sign-cart schema truncated mid-property definition, making CartMandate structure impossible to validate from the interface alone
AP2-specific tools (ap2-get-mock-payment-data, ap2-sign-cart) include conditional usage restrictions in descriptions ('Only call this tool when using AP2') that agents may not respect without explicit validation logic
select-shop description indicates internal state mutation ('internally updates the session') but does not confirm whether this persists across tool calls or requires explicit session management
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-04-14 | C | 66 | 2025-06-18 | v1 |
Selects a shipping line for the order and recalculates taxes. Maps to POST /checkouts/:id/shipping_lines endpoint.
Accepts a payload including the agent-specific shop identifier (store-name or similar from the product catalogue), and if found by the supplied identifier internally updates the session to select that shop for subsequent tool calls. Determines whether Bold Checkout supports the merchant / store, and hydrates required data shop data for subsequent order management activities against that shop. Call this tool once a user has selected products from a catalogue or otherwise chosen a store or merchant they would like to shop with. Always call this tool whenever the user seeks to shop against a different merchant.
Informs the caller whether the Bold Checkout MCP server is routing and serving tool calls as expected.
Updates customer information including name, email, phone, marketing preferences, and saved addresses. Maps to PUT /checkouts/:id/customer endpoint.
Updates an existing checkout order with desired state (customer, items, addresses). The server computes differences and applies updates intelligently. Supports adding/updating/removing items, updating customer info, shipping/billing addresses.