List the shopping lists / pantries the authenticated user can access. Read-only. Returns an array of list objects each with uuid, name, and the user's role on that list — use a returned uuid as the listId argument for every other tool here.

List all items currently on the shopping list for listId. Read-only. Returns an array of ArticleDto objects (uuid, name, amount, unitId, categoryUuid, pantrySettings, …); empty array if the list is empty. For pantry items use list_pantry_items; to add a new shopping item use add_shopping_item.

Add an item to the shopping list by name. The API matches name against the user's article catalog: an existing article is reused (its category, unit and price history preserved); a new article is created on first use. Returns the resulting ArticleDto. To add directly to the pantry instead use add_pantry_item; to mark an existing shopping item bought use check_shopping_item.

Check off a shopping-list item. The list's settings decide the actual effect: markDone flags the item as bought (stays on the list, struck through), removeOnCheck deletes it, and moveOnCheck transfers it into the pantry. Mutates state and returns the updated row. To unconditionally remove regardless of list settings use delete_shopping_item; for stock changes on a pantry item use reduce_pantry_amount.

Remove an item from the shopping list, unconditionally and irreversibly (no soft-delete, not affected by list removeOnCheck setting). Returns a confirmation string; the row is gone after the call returns. Use check_shopping_item instead if you want list-setting-dependent behaviour (mark done / move to pantry) rather than a hard delete.

List all items currently stocked in the pantry for listId. Read-only. Returns an array of ArticleDto objects (uuid, name, amount = current stock, unitId, pantrySettings.earliestBestBefore for expiry tracking, minimumAmount, …); empty array if the pantry is empty. For shopping items use list_shopping_items; for stock changes on an existing item use reduce_pantry_amount; for metadata changes use update_pantry_item.

Add a new item to the pantry by name. The API matches name against the user's article catalog: an existing article is reused (its category, unit, price history preserved); a new article is created on first use. Returns the resulting ArticleDto. Use reduce_pantry_amount to change stock on an item already in the pantry; use update_pantry_item to rename or change unit / category; use add_shopping_item to put it on the shopping list instead.

Change the stock of an existing pantry item by a delta. Mutates state and returns the updated ArticleDto. If autoRestock is true and the new amount lands at or below the item's minimumAmount, the item is also added to the shopping list in the same call. Use add_pantry_item to create a new pantry entry; use update_pantry_item for metadata (name / unit / category) — this tool only touches stock.

Update an existing pantry item's metadata (rename, change unit, category, brand, notes). Internally fetches the current ArticleDto and PUTs back a merged copy — only the fields you pass change; everything else (current stock, price history, image URLs, autoRestock config) round-trips unchanged. Two API calls per invocation. Returns the updated ArticleDto. Use reduce_pantry_amount for stock changes — this tool only touches metadata.

Search the user's recipes (their own creations + public favourites) by free-text and optional category filters. Read-only and paginated — returns { results: RecipeDto[], totalCount, totalPages, currentPage }. To fetch a single recipe by uuid use get_recipe; to delete one you own use delete_recipe.

Get a single recipe by its uuid. Read-only. Returns a full RecipeDto with name, description, ingredients[], steps[], imageUrls[], totalTime, categories[], etc. Use search_recipes to discover recipe uuids; use delete_recipe to remove one you own.

Delete a recipe you own, unconditionally and irreversibly. The API rejects deletes for recipes belonging to another user with a 403; that error surfaces verbatim to the caller. Preview with get_recipe before calling to confirm authorship and contents.

List meal-plan entries between two dates (inclusive). Read-only. Returns an array of day objects — [{ date, list: [{ type: "recipe" | "manual", uuid?, name? }, …] }, …] — one per day that has any entries. Days with no plan are omitted from the response (so an empty array means nothing is planned in the range, not that the range is invalid). To set or clear a single day use update_week_plan_day.

Replace the meal-plan entries for one day, identified by date. list is a full replacement — the day's previous entries are discarded. Pass an empty array to clear the day entirely. Returns the new { date, list }. To read a date range use get_week_plan; to read a single recipe referenced in the plan use get_recipe.