BurnWeek

Marks a day closed in BurnWeek when the user is done eating for it: 'close the kitchen', 'close today', 'that's it for today, I'm done eating'. Today by default, or a past date. Closing again keeps the first close time, and later logging does not reopen it; reopen:true opens the day again. Changes no meals, targets or library items. Not for logging food, reminders or a future day. Returns the date, closed and the first close time (closedAt).

close_today

Removes a logged meal, or some of its items: 'delete the salad I logged', 'undo that' / 'scratch that, I didn't eat it' (the meal just logged), 'take the rice out of that' / 'I didn't have the fries' (componentIds removes only those items), or food logged but not eaten after all ('I skipped the dessert after all'). Acts on meal and item ids from earlier results; accepts the legacy timestamp id. Removing the last item deletes the meal. Not for changing amounts or names. Returns the day state after removal, and the surviving meal when items were removed.

delete_meal

Removes something saved: a recipe, a favourite, a recurring rule, or a meal from a day's plan — 'unstar', 'stop repeating', 'take that off tomorrow' (kind=planned needs date), a saved routine the user stopped, or a saved dish they no longer want kept. Not for logged meals or for skipping a single day of a recurring rule. Returns removed, the item's name and the remaining rows for that kind.

delete_saved_item

Corrects a logged meal: 'make the rice 200 g', 'the potatoes were 350 cal', 'add 20 g butter to that', 'it had cheese too', 'rename it', 'that was dinner', 'that was yesterday'. Covers per-item edits (updateComponents), new items (addComponents), splitting a meal into its ingredients in one atomic step (replaceComponents), rename, meal type, day move and a whole-meal rescale (portionGrams). Renaming one item to a different food swaps that ingredient: only it is re-priced, at the same weight; user-stated values are stored verbatim. removeComponentIds + addComponents swaps items atomically; preview:true shows the meal and day before → after without saving, confirmPreviewId applies that preview once, cancelPreviewId discards it. expectedRevision guards against stale edits. Not for deleting the meal or for logging a new meal. Returns the updated meal and day state, or the preview.

edit_meal

Reports what happened to feedback the user sent to BurnWeek: 'did they fix my bug report?', 'status of my feedback'. Read-only; the user's own reports only. Not for sending feedback. Returns each report's status — received (not reviewed yet), triaged, planned, in_progress, fixed, wont_fix or duplicate — with the team's note; only fixed means resolved.

get_feedback_status

Searches what BurnWeek already knows about the user's food — favourites, frequent meals, recent meals (with ids), saved recipes, scanned barcodes, recurring rules — to find or re-log it ('what I had last time', 'my usual', 'that soup I made'), or fetches one logged meal in full by mealId (componentIds, revision). Without a query it browses; kinds limits it to some libraries. It matches the user's words across languages, spellings and mis-hearings against their history, own foods first, so it resolves item names that sound personal, branded, misheard or unfamiliar. Not for logging new food or generic nutrition questions. Returns rows per kind, the meal when mealId was given, and ready-to-log entries for the top matches.

find_food

Use this when the user wants to connect their existing BurnWeek app data to ChatGPT and gives you a link code from the BurnWeek app. Links this ChatGPT identity to their BurnWeek account.

link_account

Use this when the user ate or drank something and wants it logged: 'I had a chicken bowl', '300 g potatoes, ~390 cal', a food photo, 'log my protein bar', 'same as yesterday's lunch', 'half of my lentil soup'. Also handles: photos (imageUrl/imageData), saved barcodes, favourites, recipes and re-logging a meal via `from` — exactly one source per call. Pass what you know as `components` with provenance; BurnWeek estimates only the blanks. ALWAYS pass the user's local `date`. Use also when BurnWeek is not named but the user reports their own food as eaten ('just had two eggs and toast', 'grabbed a latte'). Do not use for hypothetical questions ('calories in a Big Mac?') or for correcting an entry (edit_meal). Returns the meal, its totals and the full day state. Tip: read `next[]`.

log_meal

Plans food for a day that hasn't happened yet: 'plan a chicken bowl for tomorrow', 'add salmon to Wednesday', 'tomorrow I'll have the salmon'. A planned meal counts toward that day and becomes a real meal when the day closes. Plans from text or from a saved recipe, favourite, past meal or planned item (from); resizes a planned item (itemId + grams) or swaps it in place (itemId + text). Part of something already logged or planned ('the other half of the pot for Saturday') is copied via from.{planned|mealId|recipeId} + grams/factor, so the same food keeps the same numbers. `date` is the user's local day. Not for food already eaten, musings or meal ideas. Returns the day's plan card.

plan_meal

Saves food for later: what was cooked as a recipe (every ingredient, zero-calorie ones too, plus method, cooked weight, servings), changes to a saved recipe (rename, instructions, pin, ingredient add/update/remove by name with kind + id), or a meal or food starred as a favourite — e.g. a dish cooked together that the user wants to make again. Sources: a logged meal (from.mealId, any day), a description (text) or an ingredient list. BurnWeek estimates blanks and keeps supplied numbers with their provenance; names are in the user's language. Not for logging food eaten or planning a day. Returns the saved item with per-ingredient provenance.

save_to_library