Recipes / Guided cooking
Create a Thermomix guided recipe with AI.
Turn an ordinary recipe into a clear private Cookidoo recipe where people can read every instruction and supported machine settings remain attached to the correct step.
Short answer
Write the complete human-readable recipe first, split every ingredient action from the machine action that follows, then add validated INGREDIENT, TTS, or MODE annotations. Calculate each position against the final text before upload.
The essential rule
One kind of action per step
Cookidoo MCP deliberately enforces a two-step rhythm because it is clearer for beginners and avoids combining scale behavior with a running Thermomix action.
Step 1: Add 75 g sugar.
→ INGREDIENT annotation only
Step 2: Mill 30 seconds / speed 10.
→ TTS annotation onlyA step with INGREDIENT cannot also contain TTS or MODE. The recipe schema rejects this mixture.
Three action families
Choose the structure that matches the step
| Annotation | Use it for | Important detail |
|---|---|---|
INGREDIENT | Adding or weighing an ingredient | A nested VOLUME can hold amount, unit, unit text, and an optional range. |
TTS | Manual time, temperature, speed, or reverse | Time is seconds, speed is a string, and reverse is CCW. |
MODE | A supported Thermomix smart function | The mode name is uppercase and each mode has its own data constraints. |
Supported mode schemas currently include DOUGH, BLEND, TURBO, WARM_UP, RICE_COOKER, STEAMING, and BROWNING. A mode should only be used when it actually matches the cooking action and available machine behavior.
Why readable text still matters
The annotation does not replace the instruction. It selects a phrase such as “30 seconds / speed 10” within the instruction, so the person and the machine share the same source of truth.
Build sequence
Structure only after the recipe is final
- Collect the complete recipe.
Confirm ingredients, servings, tools, prep time, total time, and every preparation instruction.
- Adapt the method to the Thermomix.
Choose realistic order, bowl capacity, accessory use, speed, temperature, and duration. Do not invent unsupported modes.
- Make each instruction beginner-readable.
Name the ingredient, destination, action, setting, and observable result where useful.
- Separate ingredient and machine steps.
Keep weighing and adding before the operation that processes those ingredients.
- Add annotation data.
Use the exact quantity and machine settings represented by the sentence.
- Calculate UTF-16 positions.
Call
calculate_annotation_positionfor the marker in the final sentence. - Validate and upload.
Run
validate_guided_recipe_structure, correct all errors, then useupload_custom_recipe. - Read the saved recipe.
Confirm the stored instructions and attach a local, user-owned image only if desired.
Example request
Give the assistant a cooking standard
Be precise
Guided does not mean official
- This project creates structured private customer recipes; it does not turn them into official Vorwerk recipes.
- Cooking parameters remain recipe decisions. Validation can check the payload contract but cannot guarantee culinary or food-safety quality.
- Some Cookidoo behavior can depend on account or device features.
- Undocumented endpoints and editor behavior may change, which is why the project runs live contract checks.
Authored by the Cookidoo MCP maintainers. Annotation names, ranges, and separation rules checked against the schemas and verified example on 29 July 2026.