Terminal.shop MCP 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| browse-products | |
| manage-cart | |
| place-order | |
| manage-subscription | |
| manage-profile |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| products | |
| product | |
| order-history | |
| profile | |
| addresses | |
| cards | |
| cart | |
| subscriptions |
TDQS
Scored across 19 tools
Each tool has a clearly distinct purpose targeting specific e-commerce operations like cart management, payment processing, user data, and product interactions. There is no significant overlap between tools like 'add-to-cart', 'checkout', 'create-order', or 'search-products'.
All tool names follow a consistent kebab-case pattern with clear verb-noun combinations (e.g., 'add-to-cart', 'create-address', 'search-products'). The naming convention is uniform throughout the entire set without any deviations.
With 19 tools, the count is slightly high but reasonable for an e-commerce server covering cart, orders, payments, subscriptions, and user profiles. It's well-scoped for the domain, though some tools might be consolidated (e.g., address/card management).
The tool set provides comprehensive coverage for core e-commerce workflows including product search, cart operations, checkout, payments, subscriptions, and user management. Minor gaps include lack of update/delete for orders or subscriptions, but agents can work around this.