commerce-ops-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the Streamable HTTP server. Defaults to 3000. | 3000 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_ordersA | Find candidate orders to investigate, optionally filtered by status and/or customer id. Read-only lookup — not general order management. |
| get_order_contextA | Gather the operational facts for one order — order, customer, payment, items+product, inventory, fulfillment — as evidence for investigating why it may be delayed. Returns facts only, no diagnosis. |
| diagnose_order_delayA | Apply deterministic rules to an order's context to identify the most likely cause of a delay (payment issue, inventory shortage, fulfillment delay/failure, cancelled, or no issue), with supporting evidence. |
| recommend_resolutionA | Diagnose an order's delay and return recommended next actions for an operations specialist to take. |
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 4 tools
Each tool serves a distinct stage in the investigation pipeline: search for candidates, gather context, diagnose cause, and recommend actions. Even though recommend_resolution includes diagnosis, the primary outputs are clearly different, so there is no ambiguity in selection.
All tool names follow a consistent verb_noun pattern in snake_case (search, get, diagnose, recommend), making the operation of each tool predictable and easy to understand.
Four tools is well-scoped for an order-delay investigation workflow, covering the essential stages without unnecessary bloat or omissions. The count fits comfortably within the ideal 3-15 range.
The tool set covers the full lifecycle of investigating an order delay: finding candidates, gathering contextual data, diagnosing the root cause, and recommending next steps. There are no obvious gaps for the stated purpose.