Skip to main content
Glama

Add to grocery list

add_to_grocery_list

Use this when the user wants things on their shopping list. Adds individual items and/or all ingredients of saved recipes to the user's Recipe One grocery list, merging with items already there.

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": "add_to_grocery_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoIndividual items to add.
recipesNoSaved recipes whose ingredients should all be added.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish this is a safe, non-destructive, closed-world write. The description adds genuinely useful behavior beyond them: the result merges with existing list contents rather than replacing them, and recipe ingredients are expanded wholesale. It does not say what happens on duplicate items (whether amounts are summed or entries deduplicated), which is the main remaining ambiguity.

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?

Two sentences with no waste: the usage trigger is front-loaded and the action plus merge semantics follow immediately. Nothing could be removed without losing information.

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 write tool with no output schema, the definition covers the trigger, both input modes, and the merge outcome, which is what an agent needs to invoke it correctly. Duplicate-handling and any confirmation of the resulting list state are the only real 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 coverage is 100%, so item name/unit/amount and recipeId/servings are already documented, and the baseline is 3. The description contributes only the "and/or" framing, i.e. that both parameters may be supplied together, which is a marginal addition over 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?

The description names a specific verb and resource: it adds individual items and/or all ingredients of saved recipes to the user's Recipe One grocery list, and it states the merge behavior. That is enough to tell it apart from remove_grocery_items or check_grocery_items in practice, but the description never explicitly contrasts itself with those siblings.

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?

"Use this when the user wants things on their shopping list" gives a clear trigger condition, and the two supported modes (loose items vs. recipe ingredients) are spelled out. It stops short of stating when NOT to use it or naming an alternative tool, so it falls under the 5 benchmark.

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