Dillr

Done shopping — removes all checked items from the shopping list. The list stays active.

complete_shopping_list

Load a specialist guide for a specific task. Available guides: recipe_creation, library_discovery, kitchen_assistant. Reading a guide before starting a task produces significantly better results. Load "recipe_creation" before writing recipes, "library_discovery" for complex searches.

get_guide

Get the user's full kitchen context: inventory, kitchen state (leftovers, equipment), recent cooking history, current and upcoming menus, active shopping lists, occasions, and user memory. Load this early to ground your suggestions in the user's kitchen.

get_kitchen_context

Show the user a saved meal plan. Pass menu_id to present a specific menu's planned meals; omit menu_id to list all menus with their date range and meal count. Call this whenever the user wants to see a menu, even if you already have it from earlier in the conversation — calling the tool is how the menu is presented to them; don't reproduce it as plain text. Refer to a menu by its name (or date range) in your reply — never show the user the menu_id; it's only an identifier for tool calls.

get_menu

Show the user a recipe that already exists — a saved library recipe or an inline snapshot — by its link. Call this whenever they want to view, open, or cook one of these, even if you already have its content from earlier in the conversation (calling the tool is how the recipe is presented to them; don't reproduce it as plain text instead). For a NEW recipe you just wrote that isn't saved yet, use present_recipe instead. Returns the recipe as markdown in its original language — do not translate or modify. Accepts three link forms, all emitted verbatim by other tools (`search_recipes`, `get_menu`, `get_cooking_history`, `get_kitchen_context`): - `/recipes/{recipeId}` — a saved recipe in the personal library - `/menus/{menuId}/recipes/{recipeId}` — the inline snapshot inside a menu - `/cooking_history/{historyId}` — the inline snapshot inside a cooking history entry Copy the link substring from the source tool verbatim — no decomposition needed.

get_recipe

Frequency stats for your recipe library — how often each ingredient, cuisine, technique, or tag appears across saved recipes. Use this to discover available filter values before calling search_recipes, or to understand cooking patterns.

get_recipe_stats

Get a shopping list. Omit list_id to get the default list.

get_shopping_list

Append a cooked meal to the user's cooking history. Use after the user says they cooked something, to capture ratings and notes (e.g. substitutions, what to improve, portion adjustments) for future pattern recognition. Optionally link to a saved recipe via its `link` (from search_recipes). Does not modify the recipe itself — for that, use save_recipe.

log_meal

Show the user a NEW recipe you just wrote or found that is NOT yet saved in their library — you pass the full recipe content here and it is presented as an interactive card with step-by-step cook mode. Call this whenever the user wants to see, show, open, or cook such a recipe (including right after you generate one, and when they just say “show me” or “show it in Dillr”), and prefer it over writing the recipe out as plain text. Presenting only DISPLAYS the recipe — it does NOT save it; saving is a separate, explicit step (the card's Save action / save_recipe) that the user takes when they want to keep it. No account is required to view or cook from the card. For a recipe that already exists in the library, use get_recipe with its link instead.

present_recipe

Create or update a menu for the kitchen. **Get the user's go-ahead on the plan before you call this.** Saving a menu commits it, and each fenced ```recipe block also adds that recipe to the user's library — so present the full plan first (the meals AND the recipes you're proposing) in your reply, and call save_menu only once the user has approved. Don't propose a plan and save it in the same turn. Two modes: - **content**: Full replace — provide the complete list of meals as markdown. Requires start_date (defaults end_date to start_date + 6 days). - **changes**: Edit an existing menu with SEARCH/REPLACE blocks on its markdown. Menu format (one bullet per meal): ``` - Monday Dinner [Miso Glazed Tofu](/recipes/abc123) — Family weekday favorite - Double the glaze - Tuesday [Quick Stir Fry](/recipes/xyz789) - Dinner [Spaghetti Carbonara](/recipes/def456) — Pantry meal - [Grandma's pot roast](/recipes/ghi101) - Monday **Morning Pancakes** — Fluffy banana pancakes ``` **Every meal should be cookable — give it a real recipe, don't just name it.** For each meal, do one of: 1. **Link** a recipe the user already has — find it with search_recipes and link it by id: `[title](/recipes/{id})`. 2. **Attach a new recipe** (the default for any new dish you're proposing) — write the meal as a **bold** title and put the FULL recipe in a fenced ` ```recipe ` block directly under the meal bullet. Dillr saves it to the library and links it automatically — no separate save_recipe call. Write the actual recipe (ingredients + steps), same markdown as save_recipe — do not just name the dish: ```` - Monday Dinner **Miso Glazed Tofu** — Family favorite ```recipe # Miso Glazed Tofu ## Ingredients - 400g firm tofu ## Instructions - Press the tofu, then sear. ``` ```` A bare **bold** title with NO recipe block is only for a meal that genuinely has no recipe (leftovers, eating out) — never use it as a shortcut to skip writing a recipe the user will want to cook. Don't save a names-only plan and offer to add recipes later; write them now. - Weekday and slot (Breakfast/Lunch/Dinner) prefixes are optional and case-insensitive. - Linked meals use `[title](/recipes/{id})` from search_recipes. Menu-scoped links `[title](/menus/{menu_id}/recipes/{id})` are also accepted. - Bare-title meals (no link) require **bold** title: `- Monday **Morning Pancakes**`. Linked meals already have bracket delimiters. - Weekday and slot values must be in English (Monday–Sunday, Breakfast/Lunch/Dinner). Titles and descriptions can be any language. - Optional description after ` — ` (space, em-dash, space). - Optional indented ` - …` bullets become the meal's notes. Only call save_menu once the user has approved the plan (see the note above). Refer to the menu by its name (or date range) in your reply — never show the user the menu_id; it's only an identifier for tool calls. SEARCH/REPLACE format: <<<<<<< SEARCH (exact text) ======= (replacement) >>>>>>> REPLACE

save_menu