Unofficial Monsieur Cuisine MCP

Overview Schema Source Related Servers Discussions Admin

Get Cookidoo Recipe

get_cookidoo_recipe

Preview how one Cookidoo recipe converts to Monsieur Cuisine Smart: ingredients, steps, mapped device programs, and cover image, without creating anything.

Instructions

Preview how ONE Cookidoo recipe converts to a Monsieur Cuisine Smart recipe, without creating anything.

Accepts a Cookidoo recipe id (e.g. 'r59322') or a full Cookidoo URL (e.g. 'https://cookidoo.co.uk/recipes/recipe/en-GB/r59322'). Requires a prior cookidoo_login (or COOKIDOO_EMAIL/COOKIDOO_PASSWORD env vars).

Returns the parsed Cookidoo fields plus the converted payload: ingredients (amount/unit/name), steps with detected device programs (Thermomix '3 sec/speed 7' -> customized, '15 min/100°C/speed 1' -> customized, oven/Varoma -> roasting/steaming/slow_cooking/kneading, 'weigh N g' -> scale), mapped category/complexity ids, parsed servings/times/nutrition, and the downloaded cover-image file.

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_ref": "<recipe_ref>"
    },
    "name": "get_cookidoo_recipe"
  }
}

Input Schema

Name	Required	Description	Default
`email`	No
`country`	No
`language`	No
`password`	No
`recipe_ref`	Yes	Cookidoo recipe id or URL.
`mc_language`	No	Monsieur Cuisine locale, e.g. 'en-US'.	en-US

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it explicitly says nothing is created, discloses authentication requirements, and describes the returned converted payload in detail. It does not cover failure modes or rate limits, but the core behavioral profile is clear.

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?

The description is front-loaded with purpose and scope, then uses the second paragraph efficiently to explain conversion behavior. It is somewhat long, but the detail is largely useful rather than repetitive.

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?

The tool is complex and has a detailed output schema, so the description does not need to restate return values, though it does helpfully summarize them. The main remaining gap is the optional locale and credential parameters, which are not fully explained.

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 33%, so the description should compensate more. It adds useful detail for recipe_ref by giving id and URL examples, and it explains the login prerequisite for email/password, but it leaves country, language, and mc_language undefined and does not clarify their relationship.

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 first sentence states a specific verb and resource: preview how one Cookidoo recipe converts to a Monsieur Cuisine Smart recipe. The phrase 'without creating anything' clearly distinguishes this from mutating siblings such as import_cookidoo_recipe and create_recipe.

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?

The description makes the preview-only use case clear and states the prerequisite of a prior cookidoo_login or COOKIDOO_EMAIL/COOKIDOO_PASSWORD env vars. It implies the alternative (use the import tool when you actually want creation) but does not explicitly name that sibling.

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