Skip to main content
Glama

List menu

menu_list
Read-only

List categories and products, with each product's allergens, for a store after delivery type has been selected. Delivery type affects product availability and prices. Results come in pages of whole categories; when nextPage is set, call again with that page for more.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "storeId": "<storeId>",
      "deliveryType": "<deliveryType>"
    },
    "name": "menu_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number from nextPage; omit for the first page.
storeIdYesOkam store id.
deliveryTypeYesSelected delivery type. Use values from store_get/store_list.

Output Schema

NameRequiredDescriptionDefault
pageNo
storeIdNo
nextPageNo
categoriesNo
deliveryTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / categories / items / properties / items / items / properties / product / properties / allergens / items / properties / code
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so the description correctly focuses on non-obvious behavior. It adds real value by disclosing that delivery type changes availability and prices, and that results are paginated by whole categories rather than arbitrary slices. It does not mention rate limits or caching, but nothing is misstated.

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

Conciseness4/5

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

Three sentences, front-loaded with the core purpose, then the availability/price caveat, then pagination. Every sentence carries information; the minor cost is the 'nextPage'/'page' wording mismatch that slightly blurs the paging instruction.

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 3-parameter read tool with full schema coverage and an output schema, the description covers the prerequisite, the delivery-type effect, and the pagination loop. Return values need not be described because an output schema exists. Nothing critical to correct invocation is missing.

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; the description earns a bump by explaining the consequence of deliveryType (affects availability and prices) and the paging loop tied to the page parameter and nextPage output. The only wrinkle is that it says 'nextPage' where the input parameter is 'page', which a careful reader must reconcile.

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 (lists categories and products, including allergens) scoped to a store and a selected delivery type. That is enough to distinguish it from cart_, checkout_, and store_ siblings without opening the schema. It stops short of naming an alternative tool, but no near-duplicate sibling exists.

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 a clear precondition ('after delivery type has been selected') and paging instructions ('when nextPage is set, call again with that page'). No explicit when-not-to-use or pointer to a sibling, so it is clear context rather than full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources