Skip to main content
Glama
mealie-agent-mcp

mealie-agent-mcp

by loidolt

Add Recipe To Shopping List

add_recipe_to_shopping_list

Add all ingredients from a recipe to an existing shopping list, merging them with current items and returning unchecked entries. Use a scale multiplier to adjust for batch size.

Instructions

Add all of a recipe's ingredients to a shopping list (merged with existing items). Returns the list's unchecked items.

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": {
      "list_id": "<list_id>",
      "recipe": "<recipe>"
    },
    "name": "add_recipe_to_shopping_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNoRecipe multiplier, e.g. 2 for a double batch.
recipeYesRecipe slug or id.
list_idYesShopping list id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation. The description adds meaning beyond them by disclosing merge semantics with existing items and that the response is the list's unchecked items. It does not address duplicate handling or repeat-call behavior, keeping it below 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.

Conciseness5/5

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

Two short sentences with zero filler; the operation and its merge behavior are front-loaded, and the return-value note follows efficiently.

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 three-parameter composite write with full schema coverage, an output schema, and clear annotations, the description covers the essentials: what gets added, how it merges, and what comes back. Only edge cases like duplicate items or invalid recipe slugs are unaddressed.

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 list_id, recipe, and the scale multiplier are fully documented in the schema. The description adds no parameter-level detail (it never mentions scaling), which is the baseline for a fully covered 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: adds all of a recipe's ingredients to a shopping list. The parenthetical '(merged with existing items)' clarifies the operation's nature. It does not explicitly name the nearest sibling (add_shopping_list_items) to distinguish this recipe-based add from an arbitrary-item add, so it falls short of a 5.

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?

The description makes the intended scenario reasonably clear (adding a recipe's ingredient set), but never states when to prefer it over add_shopping_list_items or what prerequisites exist (e.g., whether the list must already exist). Usage is implied rather than explicit.

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