Better Mealie MCP

by djwmarcx

Overview Schema Source Related Servers Discussions Admin

Remote

Create Households Shopping Items

create_households_shopping_items

Add a new item to a household's shopping list in Mealie. Specify food, quantity, and unit to create the entry.

Instructions

Create One

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`food`	No
`note`	No
`unit`	No
`extras`	No
`foodId`	No
`unitId`	No
`checked`	No
`display`	No
`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.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 behavioral burden, and it discloses nothing: no auth/permission requirements, no note that this is a mutating write, no side effects, no idempotency or error behavior. A single-word fragment for a 16-parameter mutation is a serious gap.

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?

It is short, but not concise in the useful sense — it is under-specified to the point of uselessness. There is nothing to front-load because no substance is present.

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?

An output schema exists so return values need not be explained, but for a write tool with 16 intake parameters, zero annotation coverage, and a deep nested object graph (Recipe-Input, ingredient/unit/food refs), the description is entirely inadequate to call it correctly.

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 (only shoppingListId is required). The description provides no parameter meaning whatsoever, so it fails to compensate for the completely undocumented schema.

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 'Create One' restates the name's verb and, via 'One', hints at single-item creation versus the sibling create_households_shopping_items_create_bulk. It never names the resource (a shopping list item) or the parent shopping list, so it is near-tautological rather than a genuine statement of purpose.

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 when-to-use, when-not-to-use, or alternative guidance. 'Create One' implies a single-item variant exists but does not say when to pick this over the bulk sibling or the update/patch tools.

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

Deploy Server