Skip to main content
Glama
picnic-mcp

picnic-mcp

by jlb-jlb

Add a recipe to the cart

add_recipe_to_cart

Adds a recipe's required ingredients to the Picnic cart, skipping pantry items and alternatives by default; optionally include or skip specific ingredients. Does not place an order.

Instructions

Add a recipe's needed ingredients to the cart, like the app's 'add all' button. Ingredients the user probably has at home, pantry items and alternatives are left out by default. Use include_ingredient_ids (from get_recipe) to add ones the user lacks, and skip_ingredient_ids to leave out needed ones the user already has. Does not place an order.

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": {
      "recipe_id": "<recipe_id>"
    },
    "name": "add_recipe_to_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
portionsNo
recipe_idYesRecipe id from search_recipes or create_recipe
skip_ingredient_idsNo
include_ingredient_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnly=false, destructive=false, openWorld=true), and the description adds genuinely new behavior: the default ingredient-filtering policy and the fact that no order is placed. It stops short of disclosing what happens on repeat calls (idempotentHint=false) or how include_ingredient_ids and skip_ingredient_ids interact if an id appears in both.

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?

Three tight sentences: what it does and its default exclusions first, then how to override, then the explicit non-goal. No filler and nothing buried.

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 should hint at the result; it only says it doesn't place an order, not what the cart looks like afterward. Otherwise, for a 4-param mutation with thin schema coverage, the default-filtering policy and override mechanism make it callable without further guesswork.

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 only 25% — just recipe_id is documented — so the description must compensate. It does add real meaning for include_ingredient_ids and skip_ingredient_ids (including their source, get_recipe), but 'portions' is never mentioned, leaving scaling behavior and the default of 2 undocumented anywhere.

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+resource ('Add a recipe's needed ingredients to the cart') and pins the scope with the concrete 'add all' button analogy and the boundary 'Does not place an order.' The recipe-level framing inherently distinguishes it from the single-item sibling add_to_cart and from remove_recipe_from_cart.

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

Usage Guidelines5/5

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

Explicitly describes the default behavior (pantry items, probable-at-home ingredients and alternatives are excluded) and then names the two levers for changing it: include_ingredient_ids for items the user lacks, skip_ingredient_ids for needed items the user already has. It also rules out order placement, so the agent knows when this tool is *not* enough.

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