commerce-mcp-sandbox
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsC | Search the mock catalog. Prices in CNY cents (int). Read-only. |
| get_productB | Product detail by sku, incl. specs. Read-only. |
| create_orderB | Create an order. Requires receiver {name, phone, address}. Idempotency is the caller's job in this sandbox (orders are in-memory). |
| pay_orderA | Simulate a successful payment for an order. Shipping auto-advances (~5s) and delivery (~15s) so agents can exercise full flows. |
| get_orderC | Order status + event timeline (created/paid/shipped/delivered/refunded). |
| list_ordersC | List orders, optionally filtered by user_ref. |
| request_refundB | Simulate a refund for a paid/shipped/completed order (no real money). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a distinct resource-action pair: product search/detail, order create/pay/get/list, and refund. No overlaps or ambiguous boundaries; an agent can easily select the right tool.
All tools follow a consistent snake_case verb_noun pattern (search_products, get_product, create_order, pay_order, get_order, list_orders, request_refund). The convention is uniform and readable.
Seven tools is well-scoped for a commerce sandbox, covering the essential product and order operations without excess. Each tool earns its place.
The surface covers the core commerce lifecycle: product search/detail, order creation, payment, status, listing, and refund. Minor gaps exist (e.g., no order cancellation or update), but agents can work around these for typical sandbox flows.