tekweld-ecommerce-mcp
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_mega_menuA | Fetches the raw mega menu payload from the Tekweld ecommerce test API (GET /home/get_mega_menu). Returns the full nested collections tree as-is. |
| list_menu_itemsA | Fetches the mega menu and returns a flattened, human-readable list of every menu item with its hierarchy path (e.g. 'Men > Shirts > Casual'), link, and whether it requires login or has sub-items. Easier to scan than the raw tree. |
| call_ecommerce_apiA | Generic passthrough tool for calling other endpoints under https://ecommercetest.tekweld.com/api/v1. Use this to reach endpoints not covered by a dedicated tool. Provide a path relative to the base URL (e.g. '/home/get_banners'), an HTTP method, and optional query params / JSON body / headers. |
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 3 tools
The three tools are clearly distinct: `get_mega_menu` and `list_menu_items` serve different presentation needs for menu data, while `call_ecommerce_api` is a generic fallback. No overlapping functionality, though the two menu tools share a domain.
All tool names follow a consistent `verb_noun` pattern using snake_case. However, `call_ecommerce_api` is less specific than the menu-focused names, causing a slight deviation in specificity.
With only 3 tools, the server feels thin for a general ecommerce API, but the inclusion of a generic passthrough mitigates the need for many dedicated tools. Still, it is borderline small.
The server provides dedicated tools only for the menu domain, lacking tools for products, cart, checkout, etc. The generic `call_ecommerce_api` fills some gaps but leaves the surface feeling incomplete for typical ecommerce workflows.