Agent Chef

Update a recipe

update_recipe

Destructive

Edit a stored recipe to fix ingredients, add steps, change servings, tags, image or source, or publish it publicly. Only provided fields are updated.

Instructions

Edit a stored recipe: fix an ingredient, add steps, change servings, tags, image or source, or set public to publish it on agentchef.net/recipes. Only provided fields change.

Input Schema

TableJSON Schema

Name	Required	Description
`tags`	No
`steps`	No
`title`	No
`public`	No	Publish this recipe on agentchef.net/recipes (indexable, with the household's name). Imported recipes show ingredients and link to the source for steps.
`servings`	No
`image_url`	No
`recipe_id`	Yes
`source_url`	No
`description`	No
`ingredients`	No

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`tags`	No
`steps`	No
`title`	Yes
`servings`	No
`image_url`	No
`is_public`	No
`created_at`	No
`public_url`	No	Indexable public page, when published
`source_url`	No
`description`	No
`ingredients`	No
`is_favorite`	No
`image_generated`	No	Photo was generated by Agent Chef, so it is safe to show publicly
`source_recipe_id`	No	Set when this is the household's copy of a Community recipe

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.1.1Oct 3, 2026

addedInput schema / properties / public

Added value: +{
+  "description": "Publish this recipe on agentchef.net/recipes (indexable, with the household's name). Imported recipes show ingredients and link to the source for steps.",
+  "type": "boolean"
+}

addedOutput schema / properties / image_generated

Added value: +{
+  "description": "Photo was generated by Agent Chef, so it is safe to show publicly",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / is_public

Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / public_url

Added value: +{
+  "description": "Indexable public page, when published",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / source_recipe_id

Added value: +{
+  "description": "Set when this is the household's copy of a Community recipe",
+  "type": [
+    "string",
+    "null"
+  ]
+}

First observedv0.1.0Sep 7, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so safety is covered. The description adds real value beyond that: 'Only provided fields change' discloses patch semantics (as opposed to a full replace), and the publish side effect on agentchef.net/recipes is explained. It does not address whether omitted fields are preserved vs cleared beyond the partial-update claim.

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

Conciseness4/5

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

Two tight sentences, front-loaded with the verb and resource, and the partial-update rule is placed last as a qualifier. The field enumeration is dense but each item maps to a real parameter.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and annotations cover the safety profile. However, for a 10-parameter mutation tool with near-zero schema coverage, the description leaves title/description parameters unexplained and says nothing about permissions or which edits are reversible.

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

Parameters3/5

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

Schema description coverage is only 10%, so the description carries the burden. It names most editable fields (ingredients, steps, servings, tags, image_url, source_url, public), adding meaning over the bare schema, but omits title, description, and recipe_id, and gives no format details.

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?

States a specific verb ('edit') and resource ('a stored recipe') and enumerates the editable surface (ingredient, steps, servings, tags, image, source, public). This clearly separates it from create_recipe/import_recipe siblings, though it does not explicitly name any alternative.

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?

Usage is implied rather than stated: the field list and 'Only provided fields change' signal a partial-update tool, but there is no explicit when-to-use, when-not, or pointer to alternatives like create_recipe or update_recipe_preferences.

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