MCP E-commerce Server
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_productB | Create a new product with sku, name, (optional) description, price, and quantity. |
| add_product_smartA | Create a new product with smart ai generated description if missing |
| get_product_by_idA | Fetch a single product by numeric ID |
| delete_productA | Delete a product by id. Returns { deleted: boolean }. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| generate-product-description-template | create a compelling description for ecommerce products |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| products-catalog | Browse all products in the catalog |
| low-stock-products | List products with low inventory (quantity < 5) |
TDQS
Scored across 4 tools
add_product and add_product_smart have nearly identical purposes, with the latter being a superset variant (AI-generated description if missing), so an agent cannot reliably decide which to call. delete_product and get_product_by_id are clearly distinct, but the create pair creates real misselection risk.
Names are snake_case verb_noun (add_product, delete_product, get_product_by_id), which is mostly consistent. The '_smart' suffix and '_by_id' qualifier are minor deviations but remain readable and follow the overall pattern.
Four tools is on the thin side for an e-commerce product server. It's borderline rather than extreme, but the surface feels under-scoped given the domain.
There is no update operation (price/quantity/description changes) and no list/browse products capability, leaving only create (twice), delete, and get-by-id. These gaps will cause agent failures for common catalog management workflows.