Skip to main content
Glama
Sign In
tekweld-ecommerce-mcp

tekweld-ecommerce-mcp

by akshayadeodiaspark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List mega menu items (flattened)

list_menu_items

Fetches the mega menu and presents each item in a flattened list with its hierarchy path, link, and login requirement, making it easier to scan than the raw tree.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_menu_items"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full behavioral burden. It uses 'Fetches' indicating a read operation, but does not explicitly state it is non-destructive, nor does it mention authentication needs, rate limits, or potential side effects. The description adds some value by describing the output format but lacks comprehensive behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two sentences, front-loaded with the main purpose. Every sentence adds value without repetition or unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters and no output schema, the description explains the output structure sufficiently (flattened, human-readable, fields). However, it does not mention whether the list is complete or limited, or if there is any ordering. Overall, it is adequate for a simple list retrieval tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has no parameters, so schema description coverage is 100%. The description adds meaning by explaining what the returned list contains (hierarchy path, link, login requirement, sub-items), which is helpful for understanding the tool's output. With zero parameters, a baseline of 4 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool fetches the mega menu and returns a flattened list with hierarchy path, link, login requirement, and sub-items. It distinguishes itself from the raw tree by stating it's easier to scan, implying a sibling tool get_mega_menu for raw tree.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool (when a human-readable flattened list is needed) versus the raw tree (get_mega_menu) by saying 'Easier to scan than the raw tree.' This provides clear context, though it doesn't explicitly mention the sibling tool name or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools