haus

update_meal_plan

Update a planned meal. Only the fields you send change. recipeId links a recipe and clears any custom name; name makes it custom and clears the link; recipeId wins if both are sent.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Entry id from list_meal_plans.
`date`	No	Date, YYYY-MM-DD. Must be today or within the next 28 days, so work it out from today's date.
`name`	No	Custom meal name when no recipe is linked.
`notes`	No	Free-text notes.
`mealType`	No	Meal slot of the day.
`recipeId`	No	Recipe id from list_recipes or list_global_recipes.
`servings`	No	Servings, 1-100.
`recipeSource`	No	Use 'global' when recipeId came from list_global_recipes. Defaults to 'household'.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedSep 8, 2026

changedInput schema / properties / date / description

Previous value: -"Date of the planned meal (format: YYYY-MM-DD). Must be from today up to four weeks ahead. Omit to leave unchanged."New value: +"Date, YYYY-MM-DD. Must be today or within the next 28 days, so work it out from today's date."

removedInput schema / properties / date / examples
```
Removed value: -[
-  "2026-07-16"
-]
```

changedInput schema / properties / id / description

Previous value: -"ID of the meal plan entry to update (from list_meal_plans)"New value: +"Entry id from list_meal_plans."

changedInput schema / properties / mealType / description

Previous value: -"Which meal slot of the day this entry occupies. Omit to leave unchanged."New value: +"Meal slot of the day."

changedInput schema / properties / name / description

Previous value: -"Custom meal name when no recipe is linked"New value: +"Custom meal name when no recipe is linked."

addedInput schema / properties / name / examples
```
Added value: +[
+  "Leftover curry"
+]
```

changedInput schema / properties / notes / description

Previous value: -"Optional free-text notes about the planned meal. Omit to leave unchanged."New value: +"Free-text notes."

addedInput schema / properties / notes / examples
```
Added value: +[
+  "Double the rice"
+]
```

changedInput schema / properties / recipeId / description

Previous value: -"ID of an existing recipe (from list_recipes or list_global_recipes)"New value: +"Recipe id from list_recipes or list_global_recipes."

changedInput schema / properties / recipeSource / description

Previous value: -"Set 'global' when recipeId refers to a Discover/global recipe (from list_global_recipes); defaults to 'household'"New value: +"Use 'global' when recipeId came from list_global_recipes. Defaults to 'household'."

changedInput schema / properties / servings / description

Previous value: -"Number of servings for the planned meal. Between 1 and 100. Omit to leave unchanged."New value: +"Servings, 1-100."

Changed12 schema fields changedJul 14, 2026

addedInput schema / examples

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

changedInput schema / properties / date / description

Previous value: -"Date of the planned meal (format: YYYY-MM-DD)"New value: +"Date of the planned meal (format: YYYY-MM-DD). Must be from today up to four weeks ahead. Omit to leave unchanged."

addedInput schema / properties / date / examples
```
Added value: +[
+  "2026-07-16"
+]
```

addedInput schema / properties / id / description

Added value: +"ID of the meal plan entry to update (from list_meal_plans)"

addedInput schema / properties / id / examples

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

addedInput schema / properties / mealType / description

Added value: +"Which meal slot of the day this entry occupies. Omit to leave unchanged."

addedInput schema / properties / mealType / examples
```
Added value: +[
+  "dinner"
+]
```

addedInput schema / properties / notes / description

Added value: +"Optional free-text notes about the planned meal. Omit to leave unchanged."

addedInput schema / properties / recipeId / examples

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

addedInput schema / properties / recipeSource / examples
```
Added value: +[
+  "household"
+]
```

changedInput schema / properties / servings / description

Previous value: -"Between 1 and 100"New value: +"Number of servings for the planned meal. Between 1 and 100. Omit to leave unchanged."

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

First observedJun 30, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description goes well beyond the annotations by explaining the partial-update behavior ('Only the fields you send change'), the interplay between recipeId and name, and the precedence rule when both are sent. This is valuable behavioral context that annotations do not provide and is not contradicted by readOnlyHint=false or destructiveHint=false.

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 concise sentences carry significant information with no filler. The first sentence states the core action, the second explains the update model and field precedence. Every word earns its place.

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

Completeness5/5

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

Given the 100% schema coverage, output schema presence, and annotations, the description covers the critical interaction semantics that are not discoverable from schema alone. Nothing essential is missing for an agent to invoke the tool correctly.

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 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema by specifying that recipeId clears a custom name, name clears the recipe link, and recipeId wins if both are present. This extra guidance justifies a score above baseline.

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 uses a specific verb and resource ('Update a planned meal') that clearly identifies the operation and distinguishes it from create_meal_plan, delete_meal_plan, and list_meal_plans. The partial-update detail further sharpens what the tool does without ambiguity.

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 explicit: the description indicates this is for updating an existing planned meal, but it does not name alternatives or state when not to use this tool versus create_meal_plan or delete_meal_plan. The field-behavior rules are helpful for how to call it, but not for when to choose it.

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?