Cookidoo MCP Server

Overview Schema Source Related Servers Discussions Admin

Copy Recipe To Custom

copy_recipe_to_custom

Copies a Cookidoo catalogue recipe into a new custom recipe on your account so you can adapt it without changing the original. Each call creates a separate copy.

Instructions

Copy a Cookidoo catalogue recipe into a new custom recipe on the user's account, to adapt it. Returns the new custom recipe ID: read it with get_custom_recipe, edit it, and save it with update_custom_recipe. The catalogue recipe is not changed. Each call creates another copy.

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

Input Schema

Name	Required	Description	Default
`servings`	No	Serving size of the copy (default: that of the original)
`recipe_id`	Yes	Cookidoo catalogue recipe ID (e.g. "r59322")

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Nov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the annotations, it discloses that the catalogue recipe remains unchanged and that each call creates another copy, which is important duplicate-creation behavior. It does not cover error cases or authorization requirements, but the annotations already establish the non-read-only, non-destructive profile.

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?

The description is three tight sentences with no wasted wording. It is front-loaded with the core action and then adds workflow and side-effect context.

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 simple two-parameter copy tool with an output schema, the description supplies the missing behavioral context: what is created, how to continue afterward, and that repeated calls create duplicates. The remaining details, such as servings default behavior, are already covered by the schema.

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 the input schema already documents recipe_id and servings. The description does not add syntax or meaning beyond what the schema provides for these parameters, so baseline 3 is appropriate.

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?

The description states a specific verb and resource: copy a Cookidoo catalogue recipe into a new custom recipe on the user's account. It also distinguishes the operation from catalogue mutation by saying the catalogue recipe is not changed.

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?

It gives a clear workflow for adapting a recipe: copy it, read the new ID with get_custom_recipe, edit it, and save with update_custom_recipe. It does not explicitly state when not to use this tool versus related siblings, so it is strong but not complete.

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