Log a requested meal
log_mealUse this first for a new meal the user asks to log. Consider ALL 54 supported nutrients, including fibre, sugars, fats/omegas, every vitamin and mineral, choline and essential amino acids. Use reliable food-composition information for estimates; preserve label-only/supplied values. Show a brief food/portion, kcal and P/C/F summary with source/estimate assumptions, then save immediately in this single call without asking again for the requested save. Include every supported nutrient in the payload; the short summary must not limit saved values to macros. Show a full nutrient table only when requested. Use one batch lookup_foods call for ingredient composition when needed, reusing already known matches. Put common nutrients at entry level and other fields in entry.nutrients, all per referenceQuantity. Never fill unknowns with zero. Inspect nutrientCoverage in the response and disclose gaps. Use explicit local date/timestamp and exact portions; clarify essential ambiguities. A fresh UUID request_id identifies the meal: reuse it unchanged if retrying after an uncertain result, to prevent duplicates. Prepares and saves atomically when routine saves are enabled. Otherwise returns saved:false with the website review link; never automate approval. A saved:true receipt proves completion; no mandatory follow-up read. For multiple meals call sequentially. Use get_meal and prepare_change for edits. Cannot delete or grant access.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"request_id": "<request_id>",
"date": "<date>",
"timestamp": "<timestamp>",
"entry": "<entry>"
},
"name": "log_meal"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | ||
| entry | Yes | ||
| timestamp | Yes | ||
| request_id | Yes |