Skip to main content
Glama
Tandoor Recipes MCP

Tandoor Recipes MCP

List shopping lists

list_shopping_lists
Read-onlyIdempotent

Retrieve the named shopping lists in a space, such as one per store, with IDs, names, descriptions, and colors so agents can identify the right list for shopping tasks.

Instructions

List the named shopping lists of this space (for example one per store), as {id, name, description, color}. Every member of the space sees the same lists. Optional: page, page_size.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
formatNoslim (default) returns a compact shape. full returns the raw Tandoor object.
page_sizeNoResults per page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.4.4
    • addedInput schema / properties / page / description
      Added value: +"Page number, starting at 1."
    • addedInput schema / properties / page_size / description
      Added value: +"Results per page."
  2. Changed1 schema field changedv3.4.1
    • addedInput schema / properties / format / description
      Added value: +"slim (default) returns a compact shape. full returns the raw Tandoor object."
  3. First observedv3.4.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuine context beyond that: the lists are space-shared and identical for every member, and the result shape is spelled out. It omits pagination semantics (whether total counts or cursors come back), which keeps it short of a 5.

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?

Front-loaded with the resource and scope, then the return shape, then the optional params — no wasted sentences. The trailing 'Optional: page, page_size' duplicates the schema and names only two of the three parameters, so it isn't perfectly economical.

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?

With no output schema, the description usefully declares the returned fields {id, name, description, color}, which is exactly what an agent needs. The remaining gap is the undocumented 'format' parameter, which can change the returned shape the description just promised.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents page, page_size and format, making 3 the baseline. The description notes page and page_size as optional but adds no syntax or defaults, and it never mentions the existing 'format' enum (slim/full), so it adds little and is incomplete relative to the schema.

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?

States a specific verb and resource ('List the named shopping lists') plus an explicit scope ('of this space') and the returned fields. The 'named ... lists' framing plus the store example clearly separates it from entry-level siblings such as list_shopping_entries.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the discovery step before adding or checking entries, but the description names no alternative and gives no when-not-to-use condition. It also doesn't say what to do if you need entries rather than lists, leaving that routing to inference from sibling names.

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