BurnWeek

Use this when the user shares a photo of their food and wants it logged (e.g. 'log this', 'what's in this photo'). Pass the image as `imageUrl` (a URL BurnWeek can fetch) or `imageData` (base64). BurnWeek's vision model estimates the calories, protein and macros from the photo — never estimate them yourself. Returns honest calorie/protein ranges plus how the day is tracking.

log_photo

Use this when the user wants to log a portion of one of their saved recipes (e.g. 'log my lentil soup', 'add 300g of the chicken bowl'). Identify the recipe by `recipeId` (preferred) or `name`. Scale it with `portionGrams` (grams of the finished dish eaten) or `fraction` (share of the whole, 0–1); omit both to log the whole recipe. Every ingredient is scaled proportionally — BurnWeek's stored estimates are used, never new ones.

log_recipe

Use this when the user wants to log one of their saved scanned products/barcodes (e.g. 'log my protein bar', 'add 150g of the greek yogurt'). Identify it by `code` (preferred) or `name`. The calories are pure math from the product's per-100g nutrition × grams — no AI estimate. Defaults to a 100g serving.

log_barcode

Use this when the user wants to PLAN a meal for today or an upcoming day (e.g. 'plan a chicken bowl for tomorrow', 'add salmon to my plan Wednesday'). BurnWeek estimates the calories and protein and books the meal onto that day's plan — a planned meal counts immediately and turns into a real logged meal when the day closes. This does NOT log a meal for right now (use log_meal for something the user actually ate). Returns the updated plan card for that day.

plan_meal

Use this when the user wants a look across the next few days of planning (e.g. 'what's my week looking like', 'show my upcoming plans', 'plan overview'). Shows the rolling 3-day horizon as a day-tab strip with each day's planned calories, opened on the first day.

plan_horizon

Use this when the user wants to unstar/delete one of their saved favorites (e.g. 'remove my latte from favorites', 'delete that favorite'). Removes the favorite with the given id (and its duplicates).

remove_favorite

Use this when the user wants to stop a recurring meal for good (e.g. 'remove my morning oats', 'delete the recurring shake', 'stop repeating that'). Identify the rule by its recurringItemId. This deletes the rule permanently — to skip just one day use skip_recurring instead.

remove_recurring

Use this when the user wants to drop ONE food item from a logged meal (e.g. 'take the rice out of that', 'I didn't have the fries'). Removes that component and recomputes the meal totals. Removing the meal's last ingredient deletes the whole meal. Re-renders the meal card.

remove_ingredient

Use this when the user wants to remove or drop a meal from a day's plan (e.g. 'remove the salmon from tomorrow', 'take that off my plan'). Removes one planned item by id; if it was the last item the whole day's plan is cleared. Returns the updated plan card.

remove_planned_meal

Use this when the user wants to change the TOTAL weight of a whole meal (e.g. 'I actually ate 350g of that', 'make the whole plate 500g'). Every ingredient scales proportionally — calories and protein are recomputed, never re-estimated. To change just one item's weight use adjust_meal_grams instead. Re-renders the meal card.

rescale_meal

Use this to save a reusable recipe. Two ways: (a) turn a just-logged meal into a recipe by passing its `fromMealTimestamp` (reuses that meal's ingredients — lowest friction), or (b) build one from `components` the user described (name + calories, optionally grams + protein). BurnWeek estimates calories — never invent them. The recipe is saved to the user's Library, scoped to their account.

create_recipe

Use this when the user tells you their daily calorie/protein goal, or wants to change their target (e.g. 'set my goal to 1900 calories and 150g protein', 'my target is 2200 kcal'). Saves it on the BurnWeek server so it syncs with the app and every day's 'calories left' becomes real.

set_goal

Use this when the user wants a meal to repeat on a schedule and log itself automatically (e.g. 'make my morning oats a daily recurring', 'log a protein shake every weekday at breakfast', 'repeat this'). Two ways: (a) turn a just-logged meal into a rule with `fromMealTimestamp` (reuses its ingredients — lowest friction), or (b) describe it in `text` and BurnWeek estimates the calories. Set `schedule` DAILY or WEEKLY (with `daysOfWeek`), plus `timeOfDay`. Recurring meals count toward the day automatically.

create_recurring

Use this when the user wants to see, browse, or pick from their saved scanned barcodes/products (e.g. 'show my barcodes', 'what products have I saved', 'log one of my scanned foods'). Returns each product's name, calories per 100g and how often it's been logged. To then log one, call log_barcode with the product's barcode code or name.

list_barcodes

Use this when the user wants to see or pick from their starred/saved foods (e.g. 'show my favorites', 'what have I saved'). Opens the quick-log card on the ★ Favorites tab (with a 🕑 Frequent tab of meals they eat often) — each is a one-tap chip that re-logs it. To then log one, call log_favorite with its id or name.

list_favorites

Use this when the user wants to SEE what they've planned for a day (e.g. 'what's my plan for tomorrow', 'show my planned meals', 'what am I eating Wednesday'). Shows that day's planned meals, the planned-vs-target calorie meter, and a day-tab strip to switch days.

show_plan

Use this when the user wants to see, browse, or pick from their saved recipes (e.g. 'show my recipes', 'what recipes do I have', 'log one of my recipes'). Returns each recipe's name, ingredient count, calorie range and how often it's been logged. To then log a portion, call log_recipe with the recipe's name or favoriteId.

list_recipes

Use this when the user wants to see, review, or manage their recurring/scheduled meals (e.g. 'what recurring meals do I have', 'show my automations', 'which meals repeat'). Returns each rule's name, schedule and time, with per-row skip-today and remove actions. To change one, call skip_recurring or remove_recurring with its recurringItemId.

list_recurring

Show the logged meals and totals for a given day. This is the primary tool for RECALL — "what did I eat yesterday", "what did I have on Monday", "my calories 2 days ago" — as well as "what have I eaten today", "how many calories", "how much protein", or "how is my day tracking". Pass `date` (YYYY-MM-DD) to view ANY past day; resolve the user's relative phrase to an absolute date first. Examples: "what did I eat yesterday" → date=<yesterday's YYYY-MM-DD>; "calories last Saturday" → date=<that Saturday>; "how am I doing today" → omit date. Returns the day's meals, calorie range, protein, carbs/fat, and what's left for the day.

show_today

Use this when the user asks about their weekly calorie budget, the last 7 days, or how much headroom they have left for the week. Shows the 7-day sliding-window budget.

show_week

Use this when the user wants to skip one occurrence of a recurring meal without deleting the rule (e.g. 'skip my oats today', 'don't log the shake tomorrow'). Identify the rule by its recurringItemId; pass the `date` to skip (defaults to today). The rule keeps repeating on every other day.

skip_recurring

Use this when the user wants to remove or undo a meal they just logged (e.g. 'undo that', 'delete the last one'). Permanently removes the meal with the given timestamp.

undo_last_meal