haus

update_recipe

Update a recipe. Only the fields you send change, except ingredients, which replaces the whole existing list rather than merging.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Recipe id from list_recipes.
`url`	No	Source URL.
`name`	No	Name.
`servings`	No	Servings the recipe yields, minimum 1.
`ingredients`	No	Ingredients. Replaces the whole existing list rather than merging.
`instructions`	No	Cooking method.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`title`	No
`message`	No
`variant`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 8, 2026

changedInput schema / properties / id / description

Previous value: -"ID of the recipe to update (from list_recipes)"New value: +"Recipe id from list_recipes."

changedInput schema / properties / ingredients / description

Previous value: -"List of ingredients required for the recipe. Providing this replaces the entire existing ingredient list rather than merging with it. Omit to leave the ingredients unchanged."New value: +"Ingredients. Replaces the whole existing list rather than merging."

addedInput schema / properties / ingredients / items / description
```
Added value: +"One ingredient and its quantity."
```
changedInput schema / properties / ingredients / items / properties / name / description
```
Previous value: -"Ingredient name"New value: +"Ingredient name."
```

changedInput schema / properties / ingredients / items / properties / quantity / description

Previous value: -"Whole-number quantity of the ingredient (no fractional/unit support). Minimum: 1"New value: +"Whole-number quantity, minimum 1. No fractions or units."

changedInput schema / properties / instructions / description

Previous value: -"Free-text cooking instructions/method. Omit to leave unchanged."New value: +"Cooking method."

addedInput schema / properties / instructions / examples

Added value: +[
+  "Marinate the chicken, then simmer in the spiced sauce."
+]

changedInput schema / properties / name / description

Previous value: -"Recipe name/title. Omit to leave unchanged."New value: +"Name."

changedInput schema / properties / servings / description

Previous value: -"Number of servings the recipe yields. Minimum: 1. Omit to leave unchanged."New value: +"Servings the recipe yields, minimum 1."

changedInput schema / properties / url / description

Previous value: -"Source URL the recipe was found at. Omit to leave unchanged."New value: +"Source URL."

Changed15 schema fields changedJul 14, 2026

addedInput schema / examples

Added value: +[
+  {
+    "id": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 6
+  }
+]

addedInput schema / properties / id / description

Added value: +"ID of the recipe to update (from list_recipes)"

addedInput schema / properties / id / examples

Added value: +[
+  "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f"
+]

addedInput schema / properties / ingredients / description

Added value: +"List of ingredients required for the recipe. Providing this replaces the entire existing ingredient list rather than merging with it. Omit to leave the ingredients unchanged."

addedInput schema / properties / ingredients / items / properties / name / description
```
Added value: +"Ingredient name"
```
addedInput schema / properties / ingredients / items / properties / name / examples
```
Added value: +[
+  "chicken breast"
+]
```

changedInput schema / properties / ingredients / items / properties / quantity / description

Previous value: -"Minimum: 1"New value: +"Whole-number quantity of the ingredient (no fractional/unit support). Minimum: 1"

addedInput schema / properties / ingredients / items / properties / quantity / examples
```
Added value: +[
+  2
+]
```

addedInput schema / properties / instructions / description

Added value: +"Free-text cooking instructions/method. Omit to leave unchanged."

addedInput schema / properties / name / description

Added value: +"Recipe name/title. Omit to leave unchanged."

addedInput schema / properties / name / examples
```
Added value: +[
+  "Chicken Tikka Masala"
+]
```

changedInput schema / properties / servings / description

Previous value: -"Minimum: 1"New value: +"Number of servings the recipe yields. Minimum: 1. Omit to leave unchanged."

addedInput schema / properties / servings / examples
```
Added value: +[
+  4
+]
```

addedInput schema / properties / url / description

Added value: +"Source URL the recipe was found at. Omit to leave unchanged."

addedInput schema / properties / url / examples

Added value: +[
+  "https://example.com/recipes/chicken-tikka-masala"
+]

First observedJun 30, 2026

TDQS

A4/5.0

Behavior4/5

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

The description discloses an important behavioral nuance: partial updates are supported, and the ingredients field replaces the entire list rather than merging. This goes beyond the annotations and helps prevent accidental data loss, even though it does not describe error handling or side effects.

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?

Two succinct sentences with no filler. The main update behavior is front-loaded, and the exception about ingredients is placed immediately after, making the description easy to parse.

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 critical semantics needed to call the tool correctly: partial updates and ingredient replacement. With a complete input schema and an output schema available, the lack of error details or alternative-tool routing is acceptable, though slightly more context about prerequisites would help.

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?

Input schema coverage is 100%, so the baseline is 3. The description adds tool-level patch semantics ('Only the fields you send change') that are not captured by any individual parameter schema, clarifying that omitted optional fields are left unchanged.

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 states a specific action ('Update') and resource ('a recipe'), making the tool's purpose immediately clear. It is naturally distinguished from sibling tools like create_recipe, delete_recipe, and list_recipes by the verb and resource combination.

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

Usage Guidelines2/5

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

The description gives no explicit guidance about when to use this tool versus alternatives. It does not mention that create_recipe should be used for new recipes, or that list_recipes is the source for valid IDs, leaving the agent to infer selection from the tool name alone.

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

All haus tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?