Skip to main content
Glama

List Alphamega categories

list_categories
Read-only

List supermarket catalogue categories and product counts; omit parent for top-level or pass a path for child categories, then use returned paths as category filters.

Instructions

List catalogue categories with product counts. Without parent returns the top level; pass a path to see its children. Use the returned paths as the category filter.

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_categories"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoHow many levels below the parent to return (default 1). The full tree has about 570 entries.
parentNoCategory path to list the children of, e.g. "chilled".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare it a read-only, open-world query, so the description only needs to add operational detail — and it does: two distinct calling modes (top level vs. children of a path) and the fact that results carry product counts and reusable path strings. It does not cover result shape or whether large subtrees are paginated.

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?

Three tight sentences, front-loaded with what it returns before how to control it, and closed with the downstream workflow tip. No filler.

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?

For a two-optional-param read tool with no output schema, the description covers invocation modes and downstream use adequately. Minor gap: nothing says how the hierarchical result is shaped or whether a large subtree is truncated.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema does not: the semantics of omitting `parent` (top level) versus supplying it (children). The `depth` parameter's effect on traversal is left to the schema.

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

Purpose4/5

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

States a specific verb and resource ('List catalogue categories') and even the return content ('with product counts'). It is clearly distinct from the cart and product-search siblings, though it never names an alternative explicitly.

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?

Gives concrete operating guidance: omit `parent` for the top level, pass a path for children, and reuse returned paths as the `category` filter on other tools. It lacks explicit when-not-to-use or a named sibling, which keeps it below a 5.

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