CalorieCam

Use this when the user describes or photographs a specific meal or portion and wants its calories or macros, and does not ask to save it. Examples: "how many calories are in two boiled eggs and a slice of toast", "what are the macros in this lunch" with a photo. Pass the photo in image when the user included one. It returns the Healthier estimate card with a Save meal button. It does not save the meal or set daily targets. Saving a meal the user asked to log is nutrition.log_meal. Daily calorie or macro targets are nutrition.create_plans. Do not use for food comparisons, recipes, or general nutrition questions.

nutrition.analyze_meal

Use this when the user wants daily calorie, protein, carbohydrate, or fat targets. Examples: "how many calories and how much protein should I aim for", "help me lose weight without making this complicated", "set my targets for muscle gain", "what should I aim for after logging my meals". Creates baseline daily calorie, macro and micronutrient options. These are estimates until the user selects a plan and completes the profile form in the widget. Use only stated age and sex; omit unknown details. Stores private session plans. Does not diagnose conditions, prescribe treatment, create workouts, or manage calendars. Not for a general request to get healthier, be healthier, or a question about where to start. That is nutrition.get_healthier.

nutrition.create_plans

Use this only after the user has reviewed a personalized plan in the widget and confirmed the export. Stores that plan and profile in private Healthier onboarding. Requires a sessionId returned by nutrition.create_plans, planData from completed personalization, age, sex, height in cm, current and goal weight in kg, and activity level. If the plan, session, or profile is missing, ask the user to create and select a plan and complete the widget first. Never invent missing values.

nutrition.export_plan

Use this when someone wants to get healthier, be healthier, feel better, have more energy, or asks how to get healthier or where to start. Examples: "how can I get healthier", "I want to get healthier", "help me get healthier", "where do I start". The same request in the user's language counts, such as "ich will gesünder werden". The card asks a short check across nutrition, exercise, and recovery, then shows a simple plan. Call it with no answers filled in. The first call does not save anything. Tapping Start on the card saves one private plan link for the Healthier app. Needs no account. Do not use for "healthier than", the healthiest food, a calorie or macro target, a meal, or a logged workout. Those stay on nutrition.create_plans. General wellness for adults. Not medical advice.

nutrition.get_healthier

Use this when the user explicitly asks to save a workout they did. Requires the actual start time, the duration in minutes, and an idempotency_key so a retry saves once. Use stated calories only; omit unknown energy rather than guessing. Distance is optional. The distance unit comes from an explicit preference, the account, the region locale, or a US timezone. Does not create training plans. A request for a workout program is not this tool.

activity.log_workout

Use this when the user asks what they ate today or over recent days, or what their current daily target is. Reads meals and the current nutrition target. Defaults to seven days and allows at most thirty days per query. Earlier dates are supported. Missing records do not mean zero. Paginate with the returned cursor. The Healthier app is where the user edits entries, sees full history, or changes a target.

nutrition.get_history

Use this when the user asks to log, save, track, or add a meal they ate, or when they tap Save meal. Examples: "log my lunch of two eggs and toast", "save this meal". Pass description or image and it estimates and saves in one step, then shows the saved Healthier card. To save an earlier estimate, pass its analysis_id unchanged. A meal supplied with its own numbers needs meal, consumed_at, and an idempotency_key. Never invent nutritional values. Daily calorie or macro targets are nutrition.create_plans.

nutrition.log_meal

Use this when the user asks what they did for exercise today or over recent days. Reads workouts, steps, and synced active energy. Defaults to seven days and allows at most thirty days per query. Earlier dates are supported. Missing records do not mean zero. Paginate with the returned cursor. The Healthier app is where the user edits entries, sees full history, or changes a target.

activity.get_history