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 heavily overlapping purposes—both create a product, differing only in whether a description is AI-generated. An agent could easily pick the wrong one, and there is no guidance on when to prefer the 'smart' variant.
All names are snake_case with a verb-first pattern (add_*, get_*, delete_*), which is mostly predictable. Minor deviations exist: the 'smart' suffix and 'by_id' qualifier break the strict verb_noun mold but remain readable.
Four tools is on the thin side for an e-commerce domain and the set is dominated by creation variants. It's not egregiously small, but it feels under-scoped given the domain.
The surface covers create (twice), read-by-id, and delete, but lacks update and any list/search operation—core operations for managing a product catalog. Agents will hit dead ends when they need to modify or enumerate products.