Fitatu MCP Unofficial

Update Fitatu Meal Item

update_meal_item

Update an existing Fitatu meal item by date, meal key, and item ID. Modify quantity, measure, or custom item details and confirm the change in your day plan.

Instructions

Updates and confirms one existing Fitatu meal item selected by its exact date, mealKey, and itemId. PRODUCT and RECIPE quantity or measure changes require a measure belonging to that food definition. For CUSTOM_ITEM entries, only the name, calories, protein, fat, carbohydrates, or eaten flag can be updated; their technical measure fields are immutable. Returns { status: 'confirmed', date, mealKey, itemId } after every requested field is observed in the persisted day plan.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	Yes	Day containing the item to update, in YYYY-MM-DD format.
`fatG`	No	New non-negative fat total in grams. Accepted only for a CUSTOM_ITEM.
`name`	No	New non-empty name. Accepted only for an existing CUSTOM_ITEM.
`eaten`	No	Whether Fitatu should mark the item as eaten.
`itemId`	Yes	Meal item id to update. Use itemId returned by get_day_plan_items.
`mealKey`	Yes	Meal key containing the item. Use mealKey values returned by get_day_plan_items. Typical keys are breakfast, second_breakfast, lunch, snack, supper, but accounts with renamed or additional meals may use other keys such as dinner.
`proteinG`	No	New non-negative protein total in grams. Accepted only for a CUSTOM_ITEM.
`measureId`	No	New measure id for the item. Use measureId values returned by search_food when changing measures.
`energyKcal`	No	New non-negative calorie total. Accepted only for an existing CUSTOM_ITEM.
`carbohydrateG`	No	New non-negative carbohydrate total in grams. Accepted only for a CUSTOM_ITEM.
`measureQuantity`	No	New positive quantity for the item's current or selected measure.

Output Schema

TableJSON Schema

Name	Required	Description
`date`	Yes	Day where the updated meal item was confirmed.
`itemId`	Yes	Persisted meal item id to use in later update, move, replace, or remove operations.
`status`	Yes	The requested mutation was observed in the persisted Fitatu day plan.
`mealKey`	Yes	Meal containing the confirmed updated item.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 21, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description reveals key behaviors: PRODUCT/RECIPE measure changes require compatible measures, CUSTOM_ITEM updates are restricted to specific fields with immutable technical measures, and the tool returns a confirmed status only after persistence is observed. These are material behavioral details not visible in the annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences each carry essential information: core action and identity, item-type constraints, and return/confirmation behavior. There is no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the core behavior, item-type restrictions, measure compatibility, and confirmation semantics, which is substantial for an 11-parameter tool. It could be slightly stronger with an explicit statement of when to choose this over replace_meal_item, but the existing identity-based selection and 'updates' wording largely cover that context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the schema already documents individual parameters. The description adds cross-parameter and type-specific semantics, such as which fields are valid for CUSTOM_ITEM entries and that PRODUCT/RECIPE quantity/measure changes require a measure belonging to the food definition. This goes beyond the schema's per-property descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states a specific verb ('Updates and confirms'), the resource ('one existing Fitatu meal item'), and the exact selection key (date, mealKey, itemId). This clearly differentiates it from sibling operations like add, replace, remove, or move.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when this tool is appropriate: updating an existing meal item with exact identity fields. It does not explicitly name alternatives or exclusion conditions, but the 'existing' and 'exact date, mealKey, itemId' framing implicitly separates it from adding or replacing operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.