Skaffi

Permanently delete a recipe from the ACTIVE household (not archiving).

remove_recipe

List your accepted friends and whether each has released their food profile to you — the people you can pull into a group meal plan alongside your household members and any meal guests. Read-only. Sending or accepting friend requests and releasing your OWN profile are done by you in the Skaffi app (skaffi.de/am-tisch/freunde), not here — they are consent actions that belong to a person, not an assistant.

list_friends

List the user's households and show which one is currently ACTIVE. Use this to answer "which household am I in?" / "what households do I have?". All other tools (shopping list, pantry) operate on the ACTIVE household.

get_households

List the meal guests (account-less people) of the active household. These are the guests get_household_preferences folds into the group plan and headcount — use this to check who's included before planning, or to find the exact names to pass to remove_meal_guests.

list_meal_guests

List the saved recipes in the user's ACTIVE household (title, label, favourite, ingredient count). Use the TITLE shown here as the name argument for add_recipes_to_shopping_list, copy_recipe and remove_recipe. "(favourite)" marks THIS user's personal favourites (each member stars their own; managed in the Skaffi web app, not via these tools).

list_recipes

Plan meals on days of the ACTIVE household's weekly plan — a whole week in one call ("plan mir die Woche"). Each item gives `date` (the day to plan for, as YYYY-MM-DD) and EXACTLY ONE of: - `recipe`: the TITLE of a saved recipe (exactly as list_recipes shows it, matched case-insensitively) — links the plan slot to that recipe, so add_week_to_shopping_list can later shop for it. The recipe must be in the active household (switch_household first if it lives elsewhere). - `text`: a short free-text meal (max 200 chars) for days without a saved recipe (e.g. "Reste", "Essen gehen"). You can plan several meals on the same day (one item per meal). Lines are processed independently and answered per line. Example: [{"date": "2026-08-10", "recipe": "Spaghetti Carbonara"}, {"date": "2026-08-11", "text": "Reste"}]

plan_meals

Read the food profiles your friends have released to you — for planning a meal WITH friends (not just your household). Honours every allergy strictly, respects religious diets, avoids dislikes where possible, fits each diet. Also the right tool when asked what ONE person likes and they are not a household member: friends are not in get_household_preferences, so check here before concluding you don't know the person (#372). Read-only: you can't add friends or change who released to you here — that's done by the user in the Skaffi app (skaffi.de/am-tisch/freunde). Group-planning flow: get_household_preferences (your household) → list_meal_guests / add_meal_guests (people WITHOUT a Skaffi account) → get_friend_preferences (friends WITH a Skaffi account who shared with you) → build the menu → add_shopping_items. Do NOT also create a meal guest for a person whose friend profile you already have here — that would double them.

get_friend_preferences

Record that products were BOUGHT: each is ADDED to the pantry stock and removed from the shopping list if it was on it. Use for "I bought X (and Y and Z)" — the whole bag in one call. Prefer this for bought items because it also clears the list. When a product is on the list in several variant lines (same product, different notes), its name picks the line to clear: 'glutenfreies Brot' clears the gluten-free line, plain 'Brot' the plain one. With ONLY differing variants on the list a plain name clears none of them — repeat that one item naming the variant that was bought. For "I bought EVERYTHING / done shopping", call checkout_shopping_list once instead. If this household has the pantry turned OFF, this tool is unavailable; use remove_shopping_items to clear the items off the list. Each item: name (required, e.g. "Bananen"), and optional quantity (amount bought, default 1, added to any existing stock), unit (default Stück), category, expiry_date, expiry_source. unit and category are enums in this tool's schema. Set each expiry intelligently: a stated date ("Quark mit MHD 15.07.") → pass it as YYYY-MM-DD; a freshness hint ("Banane, schon gut braun") → estimate a realistic date (e.g. today + 2 days) and pass it; nothing said → omit expiry_date, and a default is ESTIMATED from the product's typical shelf life (a guess, not a date off the package — say so if the user asks whether something is still good). expiry_source: "package" ONLY for a date read off the packaging (or a photo of it); "estimate" — the default — for anything you calculated, freshness hints included. A wrong "package" makes a guess look verified. Lines are processed independently and answered per line. Example: [{"name": "Milch", "quantity": 2, "unit": "L"}, {"name": "Quark", "quantity": 500, "unit": "g", "expiry_date": "2026-07-15", "expiry_source": "package"}]

record_purchases

Remove items from the shopping list by name WITHOUT buying them (changed their mind, duplicates, etc.) — all in one call. For "I bought X", use record_purchases instead — it also stores the items in the pantry. Removes whole entries regardless of quantity (no partial remove). Case-insensitive and resolves catalog synonyms the same way adding does ('Klopapier' removes 'Toilettenpapier'). Since a product can be on the list in several VARIANT lines (same product, different notes — e.g. 'Brot' and 'Brot — glutenfrei'), each name decides which line: 'glutenfreies Brot' removes the gluten-free line, plain 'Brot' the plain line. If only variant lines exist and a name names none of them, that line is not removed and the variants are listed — repeat that ONE name with the variant included. Names are processed independently and answered per line. "'X' is not on the shopping list." is a normal result, not an error; do not retry it.

remove_shopping_items

Remove meal guests (account-less people) from the active household by name (case-insensitive) — e.g. the whole guest list when the event is cancelled. If unsure of the exact names, call list_meal_guests first. Names are processed independently and answered per line; "no meal guest called X" is a normal result, not an error — do not retry it.

remove_meal_guests

Remove planned meals from days of the ACTIVE household's plan ("streich Montag und Dienstag"). Each item: date (the day the meal is planned for, as YYYY-MM-DD) and name (the meal to remove — the recipe title or the free text exactly as get_meal_plan shows it, matched case-insensitively). If several meals on that day share the name, the first is removed. Lines are processed independently and answered per line. "No meal called X planned" is a normal result, not an error; call get_meal_plan to see what's actually planned.

remove_planned_meals

Save a recipe into the user's ACTIVE household so it isn't lost — whether the user supplied it, pasted a link, or approved one you proposed. In their private household it's their personal cookbook; in a shared household everyone there sees it. The `title` you set is how you'll refer to this recipe later (add_recipes_to_shopping_list, copy_recipe, remove_recipe all match on it). Write the full recipe into `body` (ingredients + steps; markdown is fine). If it came from a website, pass its URL as source_url. `label` optionally groups it (e.g. an event name). ALMOST ALWAYS pass `ingredients` as a structured list, so the user can later put them on the shopping list in one step (add_recipes_to_shopping_list, or the web button). Each entry: `name` (required, short & GENERIC — "Spaghetti", not "Barilla Spaghetti", so it merges cleanly) plus optional `quantity` (number) and `unit` (EXACTLY one of: Stück, g, kg, ml, L, Pkg). Use the closest unit; if none fits, omit it. Example: [{"name": "Spaghetti", "quantity": 400, "unit": "g"}, {"name": "Knoblauch", "quantity": 3, "unit": "Stück"}, {"name": "Salz"}]. After saving, if the user also wants to shop for it, call add_recipes_to_shopping_list(names=[<this title>]) — do NOT also call add_shopping_items for the same recipe (that would duplicate).

save_recipe

Set which SHOP the named products belong to — "Milch, Butter, Käse → Edeka" in one call. Pass an empty/null store to clear instead. apply_to picks the reach: - "trip" (the default): a per-line override for THIS trip only — e.g. re-cluster by today's offers. It needs the item to be ON the list, wins over the product's default for that one entry, and clearing it falls back to the default shop, then "no store". - "product": remember the shop as the product's DEFAULT ("Milch → Edeka") so it clusters there on every future list without setting it each time. Existing per-trip overrides keep winning for their entry. The shop is free text and remembered per household; common chains to reuse the exact spelling of: Edeka, Rewe, Lidl, Aldi, Penny, Netto, Kaufland, dm, Rossmann. Names are processed independently and answered per line. "Not on the list" / "no product called X" is a normal result, not an error — do not retry it.

set_shopping_store

Call this FIRST in a Skaffi conversation, before any other Skaffi tool. It reports this account's state — active household, who eats there, whether the pantry is on, whether friends' profiles are readable — and the tool chains that actually work for it. Accounts differ in ways that decide which tools do anything: a household with the pantry turned off refuses every pantry tool, and friends' profiles are not readable on every account. Reading that state costs one call and saves running into refusals. Safe to call again at any point — it only reads. Worth repeating after switch_household, since every line below describes the ACTIVE household.

get_started

Set the ACTIVE household by name. The active household is a single persistent selection that EVERY other tool (shopping list, pantry, preferences, guests, recipes) acts on — so switch FIRST, then act. This also moves the active household in the Skaffi web app. Matches the EXACT household name (case-insensitive): a decorated phrase like "my WG household" will NOT match a household stored as "WG". If unsure of the exact name, call get_households first. The user's personal list is a household too (usually "Deine Liste"). On "no household called X", re-read the real names rather than inventing one.

switch_household

Aggregate the food profiles of everyone eating in the ACTIVE household — every member plus any meal guests you added — with a total headcount. Call this FIRST whenever you plan food for the group (a recipe, a weekly plan, a dinner/event), then build a menu that honours every allergy strictly, respects religious diets, avoids dislikes where possible, fits each person's diet (e.g. no meat for a vegetarian), leans on shared likes/cuisines, and is PORTIONED for the returned headcount. Typical event flow: switch_household to the event's household → add_meal_guests for the attendees without a Skaffi account → get_household_preferences → propose the menu → add_shopping_items for the ingredients. SHARING (important to read the output correctly): each member chooses what to share per household, in two tiers — taste (diet/cuisines/likes/…) and sensitive (allergies + religious diet). A line may therefore say a member did NOT share, or shared taste but withheld allergies. "Not shared" ≠ "no preferences" — it means their toggle is off; they still COUNT in the headcount, so plan/portion for them and, if their diet matters, ask the user or have them enable sharing in the app. If the user names eaters not listed here, capture them with add_meal_guests and call this tool again. Diet values use this exact wording: Omnivor, Vegetarisch, Vegan, Pescetarisch, Flexitarisch. Empty fields mean unspecified — don't assume.

get_household_preferences

Return what's currently AT HOME (the pantry / stock on hand), with amounts and expiry dates. This is the source of truth for "what do I have", "can I cook X", "what did I already buy" and "what's running low / expiring". NOT the shopping list. Pass expiring_within_days to filter to what expires within that many days (including already expired), soonest first — "was läuft ab / what should I use up this week?" is expiring_within_days=7. A NEGATIVE number is meaningful and allowed: -5 lists what has been expired for at least 5 days ("was muss weg / what should I throw out?"), because the cutoff is today + days. Omit the parameter for the whole pantry. Expiry dates carry their ORIGIN: a date derived from the product's typical shelf life is marked "(estimated)"; an unmarked date was read off the package. So this is per entry, not a blanket caveat — an estimate is a planning hint, never a food-safety verdict, and for anything the user is deciding whether to still eat, the date printed on the package is what counts.

get_pantry

Return what still needs to be BOUGHT (the shopping list). This is NOT what's at home — for stock on hand use get_pantry. Use this to answer "what's on my shopping list / what do I still need to buy?". Pass group_by="store" to get the same list grouped by SHOP, so the user can split a trip ("you get the Edeka things, I'll do Netto") — the answer to "what do I buy where / group my list by store". Each item's shop is its per-line override, else the product's default shop, else the "Ohne Laden" (no store) group. To CHANGE where an item belongs, use set_shopping_store.

get_shopping_list

Read the ACTIVE household's meal plan for one week (Monday–Sunday). Use this to answer "what's the plan this week?" or before proposing changes. Each day lists its planned meals — either a saved recipe (by title) or a free-text meal. Pass `start_date` (any YYYY-MM-DD in the wanted week; it is snapped to that week's Monday) to look at another week; omit it for the current week.

get_meal_plan