Dial

Apply a user-confirmed correction to one imported food. The expectedSnapshotHash is the currentSnapshotHash from its latest receipt. Returns the updated receipt and recalculated daily totals. A stale snapshot fails without overwriting phone edits. Cannot edit unrelated native foods. Uses private request-limit and account-operation records for safe access.

update_logged_food

Read the connected account’s local date, time zone, calorie/macro goals and today’s meal groups before logging. Meal labels match Dial; numbered slots do not imply breakfast/lunch or an eating time. Never creates a daily log. Does not expose weight, medical history, or credentials. Uses private request-limit and account-operation records for safe access.

get_dial_context

Read the connected account’s current weight and one day’s stored weight in explicit lb or kg units. Defaults to today; never creates a daily log. A daily snapshot can carry a prior weight forward and is not evidence of a fresh weigh-in. Returns a snapshot hash for a safe update. Requires separate weight permission; food-only grants cannot read weight. Uses private request-limit and account-operation records for safe access.

get_weight

Read one calendar day without creating it. Includes current totals and explicit known/unknown fiber and sugar coverage. Partial nutrient totals cover only entries with known values. Uses private request-limit and account-operation records for safe access.

get_food_log

Read current state and snapshot hashes for a previously imported meal before a correction or undo. Entries changed on the phone are marked modified or missing. Uses private request-limit and account-operation records for safe access.

get_food_import_receipt

Recall the connected account’s recently used foods and remembered portions, including private connector estimates. Use for repeat meals or "my usual" before catalog or web searches. Optionally filter by name/brand. Returns last-use times and available estimate/source metadata; never includes global-popularity suggestions or claims a personal frequency count. Previous estimates remain unverified. Confirm the same product and consumed portion before preparing another meal. Uses private request-limit and account-operation records for safe access.

get_recent_foods

Prepare a private meal draft for user review and confirmation; daily totals remain unchanged. Returns proposed portions, date, macros and uncertainty. The requestId identifies one immutable proposal: retries reuse it, while changed proposals require a new ID. Uses private request-limit and account-operation records for safe access.

prepare_food_log

Change selected rows of an uncommitted meal without resending unchanged foods. Use server-issued entryId values, not source food IDs, and the latest revision. requestId identifies the new immutable proposal; reuse it for identical retries. The previous draft is superseded and cannot be committed. Daily totals remain unchanged. Show the complete returned meal and obtain confirmation of this new draft before committing. When nutrition changes, provide updated estimate/source assumptions rather than reusing stale evidence. Uses private request-limit and account-operation records for safe access.

revise_food_draft

Save the latest exact reviewed draft whose content and date the user has confirmed. The operationId identifies one save and supports retries. Returns current daily totals, that day’s goal and signed remaining amounts (negative means over target; null means unavailable), and remembers confirmed foods privately for reuse. The receipt describes current entry state; a replay with modified/missing entries does not restore them. Uses private request-limit and account-operation records for safe access.

commit_food_log

Save or replace today’s body weight only after the user explicitly requests or confirms the exact value, unit and date. Get a fresh get_weight snapshot hash first. Ask when units or intent are unclear; never estimate body weight or change it from food discussions. Preserves meals and goals other than current weight. Stale phone edits fail safely. Reuse operationId for retries; a replay reports whether that recorded weight remains unchanged, modified or missing and never restores it. Historical changes are not supported. Uses private request-limit and account-operation records for safe access.

update_weight