AI-powered Cookidoo and Thermomix recipe, shopping-list, and meal-planning automation
Strong naming conventions (all tools start with action verbs: connect_, get_, create_, update_, delete_, mark_, add_, remove_). Descriptions are comprehensive and context-aware, averaging 150-250 chars with clear prerequisites and state-change warnings. All 15 tools have documented input schemas with type definitions. However, output schemas are not explicitly documented in the source code, responses are inferred from implementation. Dry-run pattern is well-designed for mutations. Error handling is present but generic (ValueError, Exception) without actionable recovery guidance. Security: credentials loaded from .env (good), but no explicit permission gates or audit logging visible.
Add a recipe to the meal plan for a specific date. Before adding, call this tool with dry_run=true to preview. Show the preview to the user, then call again with dry_run=false to apply.
Add a custom item to the shopping list.
Authenticate with Cookidoo and store the session. This tool must be called before using other Cookidoo tools. It will: 1. Load your Cookidoo credentials from the .env file 2. Normalize and validate the optional COOKIDOO_COUNTRY and COOKIDOO_LANGUAGE values (default ro/en) 3. Authenticate with the matching Cookidoo platform localization 4. Store the authenticated session for use by other tools
Create a new custom recipe in the Cookidoo account. Before creating, call this tool with dry_run=true to preview the recipe. Show the preview to the user, then call again with dry_run=false to apply.
Delete a custom recipe from the Cookidoo account.
Output schemas not documented. Tool descriptions state what is returned (e.g., 'Get detailed information', 'Get the full text content') but do not specify the structure of response objects, field names, or types. LLMs cannot plan downstream calls or extract data reliably without knowing response shape.
Error handling is generic (ValueError, Exception) without actionable recovery guidance. Errors do not tell the LLM what to do next or categorize as retryable vs. user-fixable. Example: 'Configuration Error' message is helpful, but most error paths lack this clarity.
No explicit permission gates or audit logging. Destructive tools (delete_custom_recipe, remove_recipe_from_meal_plan) lack permission checks or audit trails. No evidence of logging who called what, when, or with what parameters.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
Get the full text content of a recipe in the account's custom recipes. Unlike get_recipe_details, this endpoint includes preparation instructions. It returns plain ingredient and instruction text; use the update tools to add or replace guided-cooking annotations.
Get the meal plan for a specific week.
Get detailed information about a specific recipe by its ID. Use this tool to get full details about a recipe for inspiration before creating your own custom recipe. You must be connected first using connect_to_cookidoo.
Get shopping-list ingredients grouped by their source recipe. By default, ingredients marked as already owned are excluded; request include_owned=true only when the full historical list is needed.
Mark a shopping-list ingredient as not owned.
Mark a shopping-list ingredient as owned.
Remove a recipe from the meal plan for a specific date.
Remove a custom item from the shopping list.
Upload or update the image for a custom recipe. Before uploading, call this tool with dry_run=true to preview. Show the preview to the user, then call again with dry_run=false to apply.
Update an existing custom recipe. Before updating, call this tool with dry_run=true to preview changes. Show the preview to the user, then call again with dry_run=false to apply.
Parameter descriptions for optional fields lack clarity on defaults and side effects. Example: 'include_owned' in get_shopping_list_ingredients defaults to false, but the description does not explicitly state this or explain the consequence of omitting it.
Dry-run pattern is well-designed but not all mutation tools document it consistently. get_meal_plan_week and get_shopping_list_ingredients are read-only, but the distinction between safe and unsafe tools could be clearer in descriptions.