retail-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RETAIL_MCP_API_KEYS | No | JSON array of key/subject/role records | |
| RETAIL_MCP_REDIS_URL | No | Shared cache URL | |
| RETAIL_MCP_ENVIRONMENT | No | Environment: development, test, or production | |
| RETAIL_MCP_DATABASE_URL | No | PostgreSQL DSN | |
| RETAIL_MCP_DATA_BACKEND | No | Data backend: memory or postgres | |
| RETAIL_MCP_STDIO_API_KEY | No | Credential for local STDIO process | |
| RETAIL_MCP_RATE_LIMIT_PER_MINUTE | No | Per-principal application limit | |
| RETAIL_MCP_REQUEST_TIMEOUT_SECONDS | No | Dependency operation timeout |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| process_orderB | Create an order atomically and decrement inventory. Requires order:write. |
| update_inventoryA | Adjust inventory with validation and audit logging. Requires inventory:write. |
| create_support_ticketB | Create a customer support ticket. Requires ticket:write. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| investigate_customer_issue | Guide a support investigation without authorizing any operation. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct domain action: support ticket creation, order processing, and inventory updating. No two tools overlap in purpose, ensuring clear differentiation for an agent.
All tools follow a consistent verb_noun pattern (create_support_ticket, process_order, update_inventory), making the naming predictable and easy to navigate.
With only 3 tools, the server feels sparse for a retail domain, which typically involves many more operations (e.g., product listings, customer management). However, the tools are focused and non-redundant.
The tools cover core retail actions (support, order processing, inventory) but miss obvious CRUD operations like reading or searching orders/inventory, creating products, or listing customers, leaving notable gaps.