E-Commerce Support Agent MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAUDE_MODEL | No | The Claude model to use, e.g. claude-sonnet-5 | |
| ANTHROPIC_API_KEY | No | Anthropic API key (required for the agent, not necessarily for MCP tools) |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_policiesA | Search company policy documents for text relevant to a question. Args: query: A self-contained search query. Conversation history is not available on this surface, so include whatever context the search needs directly in the query text. Returns: Matching policy chunks (source, section, content, relevance score) when found; grounded=False when nothing relevant enough was retrieved. |
| lookup_orderA | Look up an order belonging to an authenticated customer. Args: order_id: The order identifier, for example ORD-1002. Returns: Customer-safe order status and delivery information when the customer is authorized to access the order. |
| check_account_statusA | Retrieve the current status of a customer account. This MCP-facing tool accepts a customer ID because an external MCP client does not share the local agent's AuthContext. The calling client remains responsible for authenticating and authorizing the customer before invoking this tool. |
| list_customer_ordersA | List orders associated with a specific customer. Use this when the customer wants to view their orders but has not provided one specific order ID. The customer ID is required. |
| check_product_availabilityA | Check whether a product is currently available and return its available stock quantity. Use this when a customer asks whether a particular product is in stock. The product ID is required. |
| cancel_orderA | Cancel an order belonging to a specific customer. This is a state-changing operation, gated the same way as the in-process agent: the order must exist, must belong to customer_id, and must be in a cancellable state (Pending or Processing). Call with confirmed=False first to preview the result without cancelling anything; call again with confirmed=True only after the customer has explicitly confirmed that specific order. The calling client remains responsible for authenticating the customer before invoking this tool. |
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 6 tools
Each tool targets a distinct resource and action: account status, list orders, product availability, specific order lookup, policy search, and order cancellation. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_account_status, list_customer_orders, lookup_order). The style is uniform and predictable.
With 6 tools, the server is well-scoped for an e-commerce support agent, covering essential operations without unnecessary bloat or a thin surface.
The server covers the core support workflows: account status, order lookup and cancellation, product availability, and policy search. A minor gap is the lack of an order update or return tool, but these are often handled through separate processes.