Skip to main content
Glama
Tandoor Recipes MCP

Tandoor Recipes MCP

Update food

update_food
DestructiveIdempotent

Modify a Tandoor food record by ID to change its name, property values, and shopping lists; set or remove property types and replace list assignments while preserving other values.

Instructions

Update food (PATCH). Required: id. Optional properties[] {property_type_id, property_amount} sets one value per property type (amount null = unknown), updating the existing value of that type in place and deleting any duplicate values of that type; remove_property_type_ids[] deletes values by type. Other existing property values are kept. A type may appear once across both lists. properties_food_amount and properties_food_unit_id set the food amount the property values refer to (e.g. 100 g); properties_food_unit_id null clears the unit. Deleting a property row removes it from every food or recipe it is linked to. If a row delete fails, the food is already updated and the tool returns an error naming those rows. shopping_list_ids replaces the food's lists; [] clears them; omit it to keep them. Changing a food's lists does not change its existing shopping entries. add_recipe_to_shopping_list copies the food's lists onto new entries. create_shopping_entry without shopping_list_ids copies them when the user preference shopping_update_food_lists is on. bulk_create_shopping_list_recipe_entries without shopping_list_ids copies each food's lists whatever the user preference. Every list id is checked against list_shopping_lists first; unknown or repeated ids are rejected and nothing is written. If the lists after the write differ from the request, the tool errors and names the missing and the extra lists.

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": {
      "id": "<id>"
    },
    "name": "update_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFood ID, from list_foods.
nameNoNew food name.
fdc_idNoUSDA FoodData Central ID, used by food_fdc_lookup.
formatNoslim (default) returns a compact shape. full returns the raw Tandoor object.
propertiesNoProperty values to set, one per type.
descriptionNoFree-text description.
food_onhandNoTrue or false sets on hand for your household.
plural_nameNoPlural form, e.g. tomatoes.
shopping_list_idsNoReplaces the food's shopping lists; [] clears them.
properties_food_amountNoFood amount the property values refer to, e.g. 100.
properties_food_unit_idNoUnit ID for properties_food_amount, from list_units.
supermarket_category_idNoSupermarket category ID, from list_supermarket_categories.
remove_property_type_idsNoProperty type IDs whose values to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv3.4.4
    • addedInput schema / properties / description / description
      Added value: +"Free-text description."
    • addedInput schema / properties / fdc_id / description
      Added value: +"USDA FoodData Central ID, used by food_fdc_lookup."
    • addedInput schema / properties / food_onhand / description
      Added value: +"True or false sets on hand for your household."
    • addedInput schema / properties / id / description
      Added value: +"Food ID, from list_foods."
    • addedInput schema / properties / name / description
      Added value: +"New food name."
    • addedInput schema / properties / plural_name / description
      Added value: +"Plural form, e.g. tomatoes."
    • addedInput schema / properties / properties / description
      Added value: +"Property values to set, one per type."
    • addedInput schema / properties / properties / items / properties / property_amount / description
      Added value: +"Value per properties_food_amount; null means unknown."
    • addedInput schema / properties / properties / items / properties / property_type_id / description
      Added value: +"Property type ID, from list_property_types."
    • addedInput schema / properties / properties_food_amount / description
      Added value: +"Food amount the property values refer to, e.g. 100."
    • addedInput schema / properties / properties_food_unit_id / description
      Added value: +"Unit ID for properties_food_amount, from list_units."
    • addedInput schema / properties / remove_property_type_ids / description
      Added value: +"Property type IDs whose values to delete."
    • addedInput schema / properties / shopping_list_ids / description
      Added value: +"Replaces the food's shopping lists; [] clears them."
    • addedInput schema / properties / supermarket_category_id / description
      Added value: +"Supermarket category ID, from list_supermarket_categories."
  2. Changed1 schema field changedv3.4.1
    • addedInput schema / properties / format / description
      Added value: +"slim (default) returns a compact shape. full returns the raw Tandoor object."
  3. First observedv3.4.0

TDQS

A3.9/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true, and the description goes well beyond them: deleting a property row propagates to every food or recipe linked to it, partial failures leave the food updated and return an error naming the failed rows, list ids are validated against list_shopping_lists before any write, and list mismatches produce an error naming missing/extra lists. It also discloses that shopping entries are unaffected by list changes and which sibling paths copy lists under which user preference.

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

Conciseness3/5

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

The content is front-loaded with the verb and required parameter, which is good, but it is delivered as one dense block of run-on sentences mixing parameter semantics with the list-copy behavior of three other tools (add_recipe_to_shopping_list, create_shopping_entry, bulk_create_shopping_list_recipe_entries). That cross-tool material is informative but marginal for an agent invoking update_food and lengthens the definition considerably.

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?

For a 13-parameter destructive mutation with no output schema, the description covers the risky surfaces well: propagation of deletes, partial-write failure semantics, validation order, and list replacement rules. The main remaining gap is that it does not describe the returned food shape or how the 'format' parameter affects the response, though the schema hints at slim/full.

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?

Schema coverage is already 100%, and the description still adds real meaning: properties set one value per type, null amount means unknown, existing duplicates of that type are deleted, remove_property_type_ids deletes by type, and a type may appear once across both lists. It also explains that properties_food_amount/unit are the referent for property values and that unit null clears it. Only the format enum and the scalar text fields get no added explanation, which is fine since the schema covers them.

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

Purpose4/5

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

The description opens with a specific verb+resource pair ('Update food (PATCH)') and immediately scopes what can be changed: name-level fields, property values, property amounts/units, and shopping lists. It is clear this is a mutation of an existing food keyed by id, distinguishing it from create_food or the shopping-entry siblings, though it never explicitly contrasts itself with those alternatives.

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

Usage Guidelines3/5

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

There is no explicit 'use this when...' routing, but the description does encode the conditions that govern each optional branch ('omit it to keep them', '[] clears them', 'a type may appear once across both lists'). It clarifies how list assignment behaves relative to create_shopping_entry and add_recipe_to_shopping_list, which is helpful indirect guidance, yet an agent gets no direct statement of when to prefer update_food over other update tools.

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