ask.recipes

Send a recipe to the Thermomix

send_to_thermomix

Send one recipe to the user's Cookidoo account as a private created recipe, so it shows on their Thermomix / Bimby with guided cooking. For "send this to my Thermomix", "put it on my Bimby", "cook this on the TM6". First get_recipe, then rewrite the recipe for the Cookidoo account: name, ingredients and steps in the account's language (connect_cookidoo returns it), amounts in grams and millilitres since the Thermomix weighs everything, steps as Thermomix steps with time, temperature, speed, direction or mode. Pass name, ingredients and steps; show the user the rewritten steps before sending. Each call creates a new Cookidoo recipe. Thermomix step settings, for rewriting a recipe before send_to_thermomix: each step is one action with at most one setting block. Times are seconds. Chop: 5-10 s / speed 5-7. Sauté onion and garlic: 3-5 min / 120 °C / speed 1. Simmer sauces and soups: 15-25 min / 100 °C / speed 1, with direction CCW when pieces must stay whole. Blend soup: 1 min / speed 10. Whip cream: speed 3.5 with the butterfly, write that in the text. Melt chocolate: 50 °C / speed 2. Knead bread: mode dough for 2-3 min. Steam: mode steaming, or varoma temperature with the Varoma dish. Rice: mode rice_cooker. Modes depend on the model connect_cookidoo reports: a TM31 has none, a TM5 only dough and turbo, TM6 and TM7 all of them; on an older model write the step with time, temperature and speed instead, and the server refuses a mode the machine lacks. Keep the ingredient amounts in the step text so the screen shows them. Steps without settings are fine for prep done outside the machine.

Input Schema

Name	Required	Description
`id`	Yes	recipe id from a search, get_recipe, list_saved or upload
`name`	No	recipe name in the Cookidoo account's language; the stored name is used when omitted
`hints`	No	optional tips shown under the recipe on Cookidoo
`steps`	No	the recipe rewritten as Thermomix steps with settings, in the account's language; when omitted the recipe's plain steps are sent without settings
`machine`	No	TM31, TM5, TM6 or TM7, only when the user names a paired machine other than the connected one
`ingredients`	No	one ingredient per entry in the account's language with metric amounts in g or ml, e.g. '200 g cebola, em pedaços'; the stored list is sent verbatim when omitted

Output Schema

Name	Required	Description	Default
`url`	Yes
`name`	Yes
`cookidoo_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026
- removedOutput schema / additionalProperties
```
Removed value: -false
```

Changed1 schema field changedOct 20, 2026

addedInput schema / properties / machine

Added value: +{
+  "description": "TM31, TM5, TM6 or TM7, only when the user names a paired machine other than the connected one",
+  "type": "string"
+}

Changed3 schema fields changedOct 20, 2026

addedInput schema / properties / ingredients

Added value: +{
+  "description": "one ingredient per entry in the account's language with metric amounts in g or ml, e.g. '200 g cebola, em pedaços'; the stored list is sent verbatim when omitted",
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

addedInput schema / properties / name

Added value: +{
+  "description": "recipe name in the Cookidoo account's language; the stored name is used when omitted",
+  "type": "string"
+}

changedInput schema / properties / steps / description

Previous value: -"the recipe rewritten as Thermomix steps with settings; when omitted the recipe's plain steps are sent without settings"New value: +"the recipe rewritten as Thermomix steps with settings, in the account's language; when omitted the recipe's plain steps are sent without settings"

AddedOct 20, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The description adds key behavior beyond the annotations: every call creates a new Cookidoo recipe (consistent with idempotentHint=false), the account language comes from connect_cookidoo, and the server refuses a mode the machine lacks. It does not cover failure modes such as missing account connection or partial-send behavior, so it falls short of the richest behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The purpose and trigger phrases are front-loaded, but the description is a single dense paragraph mixing workflow instructions with a long reference catalogue of Thermomix settings. The catalogue is useful but verbose and poorly delimited, making it harder to scan than necessary.

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

Completeness5/5

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

For a mutation tool with an output schema, the description covers the workflow, prerequisite account context, language handling, machine-model constraints, rewriting rules, and the user-confirmation step. An agent has enough information to invoke it correctly in context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description goes well beyond the schema: it explains what name, ingredients and steps should contain (account language, grams and millilitres, one action per step), how machine interacts with mode support, and why ingredient amounts must stay in step text. It also clarifies the model-dependent limitations of the mode parameter, which the schema only lists as an enum.

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 (send), resource (one recipe), and destination (the user's Cookidoo account as a private created recipe) and explains the visible outcome (shows on the Thermomix/Bimby with guided cooking). This clearly separates it from sibling tools like save_recipe or share_recipe.

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?

It names the exact user phrasings that should trigger this tool and gives an explicit ordering: first get_recipe, then rewrite, show the user the rewritten steps before sending. It also explains the fallback for older machines that lack guided modes.

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

All ask.recipes tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.