Food Tracker

Search the user's food library: saved foods, recipes and batches, with ids, nutrition per 100 g, serving weight and each batch's grams left.

list_foods

Record steps, active/workout calories, workout minutes or water for a date (default today). Only passed fields change.

log_activity

Record one or more food items for a meal. Pass every item of the meal in one call. Returns the created entries and the day's running totals versus targets.

log_food

Record grams of a batch eaten by someone else. It lowers the batch's grams left and is not added to the user's food log.

log_shared_portion

Record body weight for a date (default today), with body composition when known: body fat %, skeletal muscle mass, fat mass, body water, and tape measurements. Values may be read from a smart-scale or body-composition (InBody/BCA) printout photo. One row per date: logging the same date again overwrites weight; a composition field that is omitted keeps its stored value, null clears it.

log_weight

Record that the user opened a pack (tub, loaf, jar) of a saved food, so what is left of it is counted from the portions logged since; correct what is left of the open pack; or stop counting. Returns the pack size, grams used and grams left.

open_pack

Save an ingredient or packaged product to the user's food library, or update a saved one (by id, or the same name and brand). Values are per 100 g or per serving. Returns the saved values per 100 g and per serving.

save_food

Save a reusable recipe made of saved foods with their grams, or update one (by id, or the same name; the items replace the old list). Returns its totals and nutrition per 100 g and per serving.

save_recipe

The user's meal plan: up to 12 meals plus the fixed catch-all 'other'. Each meal has a stable key, a label and an optional time window. Pass a preset (two_meals: lunch+dinner; three_meals; three_meals_two_snacks), or 'slots' as the whole plan in the order wanted: a slot without 'meal' creates a new meal (its key is derived from the label, e.g. 'Post-dinner snack' → post_dinner_snack); a known key or label updates that meal (omitted fields keep their values); meals not listed are turned off, not deleted. Use 'remove' to delete meals for good: their logged food moves to other. Renaming keeps the key and the entries.

set_meal_plan

Set calorie and macro targets per meal from a date onward (default today), for the meals in the user's plan. Pass explicit values per meal, or use_suggested: true to split the current daily target by how much each meal usually carries; explicit values override suggested ones. Explicit values patch the targets in effect: meals not mentioned keep theirs, and null clears a value. Or scale_to_daily: true to keep the current meal proportions and re-fit them to the daily target in effect. Meal targets are independent of the daily target and need not add up to it.

set_meal_targets

Set daily calorie and macro targets from a date onward (default today). Earlier days keep their old targets. Pass explicit values, or use_suggested: true to take the goal-based suggestion (suggested_targets in the profile); explicit values override suggested ones.

set_targets

Change a batch: cooked weight, name, method, date, notes, finished or not, and remove portions recorded as eaten by others. Only the fields passed change.

update_batch

Correct any field of an existing entry by id. Only the fields passed are changed.

update_food_entry

Change the goal (lose / maintain / gain), goal weight, body details, training schedule or timezone. Only the fields passed change. Returns the new energy estimate and goal-based suggested targets. Targets are not changed unless apply_suggested_targets is true.

update_profile