Skip to main content
Glama
djwmarcx

Better Mealie MCP

by djwmarcx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Update Households Shopping Items By Item

update_households_shopping_items_by_item

Update a specific item in a household shopping list by its ID, modifying details like food, quantity, unit, or checked status.

Instructions

Update One

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
foodNo
noteNo
unitNo
extrasNo
foodIdNo
unitIdNo
checkedNo
displayNo
item_idYes
labelIdNo
positionNo
quantityNo
shoppingListIdYes
accept-languageNo
recipeReferencesNo
referencedRecipeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv3.26.0
    • 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"
+}
  2. Changed3 schema fields changedv3.25.1
    • 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"
+}
  3. First observedv3.20.1

TDQS

D1.3/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 of behavioral disclosure, yet it says nothing: no mention of whether this replaces or merges fields, what happens to omitted fields, what effects or side effects occur, or what authorization is needed. 'Update' alone gives an agent no behavioral information about a mutating operation.

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 is under-specification, not conciseness — there are no sentences and nothing to structure. For a tool with a large input schema these is no meaningful content at all.

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?

Given the complexity (16 parameters, a huge schema with embedded $defs, no annotations) the description is completely inadequate. An agent cannot determine required identification fields, which fields are updatable, what the output represents, or how this differs from the many sibling tools.

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% with 16 parameters, so the description must compensate by explaining key parameter semantics. It names no parameters and does not clarify how items such as item_id and shoppingListId are identified, or how the many optional fields relate to each other.

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

Purpose2/5

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

The description is just 'Update One' — it restates the verb in the name and title without naming the resource (shopping item, household, list) or what is updated. This is effectively a tautology and does not distinguish the tool 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?

There is no guidance at all about when to use this tool versus any alternative. The sibling list includes at least four shopping/household update tools, and the description gives the agent nothing to route on.

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

Deploy Server

Other Tools