Better Mealie MCP

by djwmarcx

Overview Schema Source Related Servers Discussions Admin

Remote

Update Households Shopping Items By Item

update_households_shopping_items_by_item

Update a specific item on a household's shopping list, changing its quantity, unit, food, note, or checked status.

Instructions

Update One

Input Schema

TableJSON Schema

Name	Required	Description	Default
`food`	No
`note`	No
`unit`	No
`extras`	No
`foodId`	No
`unitId`	No
`checked`	No
`display`	No
`item_id`	Yes
`labelId`	No
`position`	No
`quantity`	No
`shoppingListId`	Yes
`accept-language`	No
`recipeReferences`	No
`referencedRecipe`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.28.0Sep 27, 2026

changedInput schema / $defs / RecipeCommentOut-Input / required

Previous value: -[
-  "recipeId",
-  "text",
-  "id",
-  "createdAt",
-  "update_at",
-  "userId",
-  "user"
-]New value: +[
+  "id",
+  "recipeId",
+  "text",
+  "createdAt",
+  "update_at",
+  "userId",
+  "user"
+]

Changed10 schema fields changedv3.26.0Sep 15, 2026

addedInput schema / $defs / CreateIngredientFood / properties / substitutions

Added value: +{
+  "items": {
+    "$ref": "#/$defs/CreateIngredientFoodSubstitution"
+  },
+  "type": "array"
+}

addedInput schema / $defs / CreateIngredientFoodSubstitution

Added value: +{
+  "properties": {
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "substituteFoodId": {
+      "anyOf": [
+        {
+          "format": "uuid",
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

addedInput schema / $defs / IngredientFood-Input / properties / substitutions

Added value: +{
+  "items": {
+    "$ref": "#/$defs/IngredientFoodSubstitution"
+  },
+  "type": "array"
+}

addedInput schema / $defs / IngredientFoodSubstitution

Added value: +{
+  "properties": {
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "substituteFood": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/IngredientFoodSummary"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "substituteFoodId": {
+      "anyOf": [
+        {
+          "format": "uuid",
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

addedInput schema / $defs / IngredientFoodSummary

Added value: +{
+  "description": "A trimmed projection of a food, with nothing on it that can recurse.\n\nSubstitutions reference this rather than the full IngredientFood, which would make\nPydantic walk food -> substitutions -> food forever and generate an equally circular\nTypeScript type.",
+  "properties": {
+    "id": {
+      "format": "uuid",
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "pluralName": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "name"
+  ],
+  "type": "object"
+}

addedInput schema / $defs / NoteReference

Added value: +{
+  "properties": {
+    "referenceId": {
+      "anyOf": [
+        {
+          "format": "uuid",
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

addedInput schema / $defs / RecipeIngredient-Input / properties / substitutions

Added value: +{
+  "items": {
+    "$ref": "#/$defs/RecipeIngredientSubstitution"
+  },
+  "type": "array"
+}

addedInput schema / $defs / RecipeIngredientSubstitution

Added value: +{
+  "properties": {
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "substituteFood": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/IngredientFoodSummary"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "substituteFoodId": {
+      "anyOf": [
+        {
+          "format": "uuid",
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

addedInput schema / $defs / RecipeNote / properties / referenceId
```
Added value: +{
+  "format": "uuid",
+  "type": "string"
+}
```

addedInput schema / $defs / RecipeStep / properties / noteReferences

Added value: +{
+  "items": {
+    "$ref": "#/$defs/NoteReference"
+  },
+  "type": "array"
+}

Changed3 schema fields changedv3.25.1Sep 8, 2026
- addedInput schema / $defs / RecipeCategory / properties / recipeCount
```
Added value: +{
+  "type": "integer"
+}
```
- addedInput schema / $defs / RecipeTag / properties / recipeCount
```
Added value: +{
+  "type": "integer"
+}
```
- addedInput schema / $defs / RecipeTool / properties / recipeCount
```
Added value: +{
+  "type": "integer"
+}
```
First observedv3.20.1Jul 10, 2026

TDQS

D1.1/5.0

Behavior1/5

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

No annotations are provided, so the description carries the full burden. It discloses nothing about mutation semantics: not which fields are replaced versus merged, whether partial updates are safe, whether unset fields are cleared, or what permissions are required.

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

Conciseness2/5

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

Two words are technically concise, but this is under-specification rather than effective brevity. There is no front-loaded scope or key constraint to anchor the agent.

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

Completeness1/5

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

For a 16-parameter mutation tool with no annotations and a flat 0% schema coverage, the description is completely inadequate. Even though an output schema exists, the input contract and side effects remain entirely undocumented.

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

Parameters1/5

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

Schema description coverage is 0% across 16 parameters, including required item_id and shoppingListId. The description provides no explanation of any parameter, so the agent must infer the meaning of ids, quantity, position, checked, recipeReferences, etc. from names alone.

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

Purpose1/5

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

"Update One" is a tautology that restates the operation without naming the resource. It does not say it updates a single shopping list item within a household's shopping list, nor distinguish it from siblings like update_households_shopping_items or update_households_shopping_lists_by_item.

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

Usage Guidelines1/5

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

No guidance whatsoever on when to use this tool versus the several closely-named shopping item siblings. Nothing about prerequisites, scoping by household/shopping list, or when to prefer bulk update.

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

Deploy Server