Skip to main content
Glama

Make a shopping list

shopping_list
Read-onlyIdempotent

One to eight uniquely identified, already-sized Dough requests. Optional unique published house pizza references and counts annotate topping needs only; they do not multiply dough. Custom flours and custom ingredients retain batch/row identity and are never merged across batches; a custom ingredient item's id is custom::. Ready starter is separate from fresh ingredients. Topping quantities are unknown. No persistence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pizzasNo
batchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / description
      Previous value: -"One to eight uniquely identified, already-sized Dough requests. Optional unique published house pizza references and counts annotate topping needs only; they do not multiply dough. Custom flours retain batch/row identity. Ready starter is separate from fresh ingredients. Topping quantities are unknown."New value: +"One to eight uniquely identified, already-sized Dough requests. Optional unique published house pizza references and counts annotate topping needs only; they do not multiply dough. Custom flours and custom ingredients retain batch/row identity and are never merged across batches; a custom ingredient item's id is custom:<batchId>:<rowId>. Ready starter is separate from fresh ingredients. Topping quantities are unknown."
    • changedInput schema / properties / batches / items / properties / dough / description
      Previous value: -"Percentages refer to total flour, except bigaHydration and starterHydrationPct. Flour rows are ratios, including empty/zero blends. Unique row IDs required. Named starter source must be a supplied row. Preferment leavening requires positive pff. No temperature inputs; preparation fixes DDT at 72 F and friction at 15 F. Buffer defaults off and non-off buffer requires balls sizing. Flour mode has no ball target: prepared ballCount/ballWeight are zero, ballsTotal is zero, bufferG is the whole batch and pizzaSize is unavailable. The 100000 g flour bound applies to direct flour inputs, not the balls solver result."New value: +"Percentages refer to total flour, except bigaHydration and starterHydrationPct. Flour rows are ratios, including empty/zero blends. Unique row IDs required. Named starter source must be a supplied row. Preferment leavening requires positive pff. No temperature inputs; preparation fixes DDT at 72 F and friction at 15 F. Buffer defaults off and non-off buffer requires balls sizing. Flour mode has no ball target: prepared ballCount/ballWeight are zero, ballsTotal is zero, bufferG is the whole batch and pizzaSize is unavailable. The 100000 g flour bound applies to direct flour inputs, not the balls solver result. Custom ingredients count by weight only and never in hydration."
    • addedInput schema / properties / batches / items / properties / dough / properties / customAdjustments
      Added value: +{
      +  "description": "Optional baker-named final-mix ingredients, up to 8, each a percentage of total flour. They count by weight only: they add to batch weight and ball sizing, never to hydration or flour absorption. Row IDs are c followed by five lowercase letters or digits, unique within the formula. Names are sent trimmed, 1 to 40 characters, unique ignoring case, and may not repeat one of Dough's own ingredient names such as Water, Salt, Oil or Sugar, or contain control, hidden or bidirectional characters or a web address. Any refused row fails the whole request.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "id": {
      +        "maxLength": 6,
      +        "minLength": 1,
      +        "pattern": "^c[0-9a-z]{5}$",
      +        "type": "string"
      +      },
      +      "name": {
      +        "maxLength": 40,
      +        "minLength": 1,
      +        "pattern": "^\\S(?:[\\s\\S]*\\S)?$",
      +        "type": "string"
      +      },
      +      "pct": {
      +        "maximum": 100,
      +        "minimum": 0,
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "name",
      +      "pct"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 8,
      +  "type": "array"
      +}
  2. Added

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; 'No persistence' largely duplicates that. The description does add non-obvious behavior: pizza references 'annotate topping needs only; they do not multiply dough', custom ingredients are 'never merged across batches', and the custom id format — genuinely useful rules an agent could not infer.

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

Conciseness2/5

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

The text is a dense run of clipped fragments ('Ready starter is separate from fresh ingredients. Topping quantities are unknown. No persistence.') that reads like schema notes rather than an agent-facing preamble. It is neither front-loaded with a purpose statement nor organized into scannable guidance.

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

Completeness2/5

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

For a tool with a deeply nested schema, 0% description coverage, and no output schema, the description should explain what comes back and how batches/flours/pizzas combine. It gestures at a few rules but omits the return shape (a list of ingredients with quantities?) and the topping-need model, leaving critical gaps.

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 0%, so the description must carry weight, and it does explain that pizzas are topping annotations rather than dough multipliers and gives the custom ingredient id syntax custom:<batchId>:<rowId>. However, it never explains the 'batches' structure or the relationship between batches, flours, and the resulting list, leaving much of the parameter semantics opaque.

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

Purpose2/5

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

The description never states what the tool produces — no verb like 'compute', 'aggregate', or 'return' a shopping list appears. Instead it opens with a restatement of the batches constraint ('One to eight uniquely identified, already-sized Dough requests'), which is parameter semantics rather than purpose. Only the name and title hint that a shopping list is generated, and nothing distinguishes it from siblings like calculate_dough or plan_bake.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus calculate_dough, plan_bake, or read_menu, and no prerequisites or ordering guidance. A reader learns constraints ('Topping quantities are unknown', 'No persistence') but not when this tool is the right choice.

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