Skip to main content
Glama
Cookidoo MCP Server

Cookidoo MCP Server

by herp75

Add Recipes To Shopping List

add_recipes_to_shopping_list

Adds the ingredients from selected Cookidoo catalogue or custom recipes directly to your shopping list, so you can shop for everything needed in one place.

Instructions

Add the ingredients of recipes to the shopping list.

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

Input Schema

NameRequiredDescriptionDefault
recipe_idsNoCookidoo catalogue recipe IDs (e.g. "r59322")
custom_recipe_idsNoIDs of the user's own custom recipes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, covering the basic safety profile. The description adds nothing beyond that: it does not say whether ingredients are appended to or replace the existing list, whether duplicates are merged, whether a Cookidoo connection is required, or what happens if both ID parameters are omitted. Those are the behaviors an agent actually needs for this mutation.

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?

A single front-loaded sentence with no redundant wording. It is efficient but extremely thin for a mutation tool, so the brevity reflects under-specification rather than discipline.

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

Completeness3/5

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

With annotations, an existing output schema, and full schema coverage, the definition covers the mechanical minimum. It is still missing the append-vs-replace semantics and the fact that both parameters are optional (0 required), leaving an agent able to call it with no IDs and unsure what state the list will end in.

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%, and both parameters are documented with examples ('r59322' for catalogue IDs, user-owned IDs for custom recipes). The description adds no meaning beyond the schema and does not clarify the practically important relationship between the two optional parameters, so it sits at baseline.

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 ('Add'), a specific payload ('the ingredients of recipes'), and a specific destination ('the shopping list'), which lets an agent distinguish it from add_shopping_list_items (raw items) and add_to_meal_plan. It stops short of explicitly naming or contrasting those siblings, so it is clear but not fully differentiated.

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 usage is implied by the action: use it when you want whole recipe ingredient sets pushed to the list rather than individual items. There is no explicit when-to-use, when-not-to-use, or named alternative such as add_shopping_list_items for one-off entries, so an agent must infer the boundary.

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