food-logging

Food logging (Morsel)

Use Morsel's MCP tools to record food, read the dashboard data, and correct entries. The current assistant analyzes an uploaded image; Morsel stores the structured result. There is no in-app chat or in-app AI.

The Morsel MCP server must be connected and the user authenticated before calling tools; writes are scoped to that account.

Scope and invariants

Use this skill for meal logging, food-history readback, profile and goal setup, nutrition recommendations based on the user's data, and corrections. Do not use it for clinical or medical diet advice.

Use it when the user sends a food photo or meal description, asks what they ate or how a day/week is tracking, asks whether they hit a target or what to eat to fit it, or asks to fix an entry.

Always follow these rules:

• Do not invent precise macros. Call search_food for exact catalog values when possible; otherwise make an honest estimate, use a lower confidence, and explain the uncertainty in the item's notes.
• Macro fields sent to log_meal are totals for the whole item as eaten, not per unit. quantity and unit are descriptive; the server never multiplies macros by them. search_food values are per its serving_size and serving_unit, so scale them yourself before logging (for example, 250 g at 130 kcal per 100 g becomes quantity: 250, unit: "g", calories_kcal: 325). If either serving field is absent, the serving basis is unknown: seek clarification or, if proceeding, use an explicitly noted lower-confidence estimate; never treat the returned macros as one serving.
• One uploaded photo is one log_meal call containing one or more items[].
• Never log twice. To reread or correct existing data, use get_day, update_meal_item, or delete_meal_log. v0.1 has no tool that adds a new item to an existing meal: if a forgotten food was part of the same sitting, confirm before deleting that meal and re-logging its complete item list once; if it was a separate meal, log it separately. Never create a second log for the same sitting.
• Choose the unit honestly: g for weighed food, ml for measured liquid, serving for a plate or portion, piece for countable food, and cup for a cup measure. unit cannot be changed by update_meal_item, so get it right on the first call.
• source is assigned by the server; never send it. A photo URL makes the server use photo_vision, a barcode without a photo makes it use barcode, and otherwise it uses manual.
• For “how am I doing” or target questions, compare the day's eaten calories with the effective goal from get_day (or get_goals when a standalone target is needed) and report the signed difference (eaten minus goal) as under, on target, or over. The effective goal is TDEE-based and activity-inclusive — activity is already factored in — so progress is eaten vs goal. get_energy_burned may be read for context and shown as a separate activity note; it is never subtracted from the goal.
• eaten_at means when the meal happened, not when the photo was uploaded. If it is unknown, omit it and let the server use now.
• Morsel v0.1 stores a caller-supplied HTTPS image_url as a reference; it does not upload or fetch image bytes. Never fabricate a URL.