Skip to main content
Glama
Sign In
Better Mealie MCP

Better Mealie MCP

by djwmarcx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Update Households Shopping Items

update_households_shopping_items

Update multiple household shopping list items in one request by sending an array of item changes to Mealie.

Instructions

Update Many

Input Schema

NameRequiredDescriptionDefault
bodyYes
accept-languageNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.30.0
    • addedInput schema / $defs / RecipeStep / properties / durationSeconds
      Added value: +{
+  "anyOf": [
+    {
+      "maximum": 2147483647,
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
  2. Changed5 schema fields changedv3.29.0
    • addedInput schema / $defs / IngredientFood-Input / properties / recipeCount
      Added value: +{
+  "type": "integer"
+}
    • removedInput schema / $defs / Recipe-Input / properties / lastMade
      Removed value: -{
-  "anyOf": [
-    {
-      "format": "date-time",
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
    • addedInput schema / $defs / Recipe-Input / properties / performTimeSeconds
      Added value: +{
+  "anyOf": [
+    {
+      "maximum": 2147483647,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedInput schema / $defs / Recipe-Input / properties / prepTimeSeconds
      Added value: +{
+  "anyOf": [
+    {
+      "maximum": 2147483647,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedInput schema / $defs / Recipe-Input / properties / totalTimeSeconds
      Added value: +{
+  "anyOf": [
+    {
+      "maximum": 2147483647,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
  3. Changed1 schema field changedv3.28.0
    • 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"
+]
  4. 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"
+}
  5. 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"
+}
  6. 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 supplied, so the description must carry the full behavioral burden and it carries none. It does not say whether this is a full replacement or partial update, whether fields omitted from an item are cleared, whether unknown item ids cause a failure, or that the body is an array of items each requiring its own id and shoppingListId.

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?

"Update Many" is terse to the point of under-specification, not conciseness. There is nothing to front-load and no structure because there is essentially no content.

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?

This is a bulk mutation over a large nested schema (item id, food, unit, quantity, position, checked, recipeReferences, referencedRecipe) with no annotations to fall back on. An output schema exists, but everything about how to invoke the tool correctly is missing.

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% and the two parameters are opaque: an untyped array of ShoppingListItemUpdateBulk objects plus an accept-language header. The description adds no meaning to either, so an agent has no help constructing the deeply nested list-item payload.

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?

"Update Many" restates the plural in the tool name without naming the resource or what is being updated. An agent only learns the target (household shopping items) from the name, not the description, and "Many" is the sole semantic addition.

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 at all on when to use this bulk update versus update_households_shopping_items_by_item or create_households_shopping_items_create_bulk. No prerequisites, no context, no alternatives.

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