Skip to main content
Glama
djwmarcx

Better Mealie MCP

by djwmarcx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Create Households Shopping Items

create_households_shopping_items

Adds a new shopping item to a household shopping list, specifying food, quantity, unit, and optional recipe references.

Instructions

Create One

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
foodNo
noteNo
unitNo
extrasNo
foodIdNo
unitIdNo
checkedNo
displayNo
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.9/5.0
Behavior2/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, but it discloses nothing beyond a fragment. It does not state whether creation overwrites, whether shoppingListId must already exist, whether food/unit references are required, or what the response contains. With zero annotation support, behavioral transparency is severely lacking.

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?

The description is extremely short, but it is under-specified rather than concise: 'Create One' is a meaningless fragment that does not front-load any useful information. A concise description should still contain a complete verb-object phrase and key constraints; this contains neither.

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 16 parameters, intricate nested $defs, a large sibling toolset, and no annotations, this description is profoundly incomplete. An agent cannot determine what to pass, how the nested food/unit objects relate to foodId/unitId, or what side effects occur. Even the presence of an output schema cannot compensate for the lack of any operational guidance.

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

Parameters2/5

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

Schema description coverage is 0% and the description is just 'Create One,' so it adds no meaning to any of the 16 parameters. The schema shows a required shoppingListId and detailed nested objects, but nothing in the description explains which fields are optional, which are core, or how food/unit references work.

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' is a truncated placeholder that gives no verb-resource clarity about creating one what—a shopping item, a household, or something else. The tool name is self-descriptive enough to infer it creates household shopping items, but the description itself fails to state the action/resource distinctly or distinguish it from siblings like create_households_shopping_items_create_bulk.

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

Usage Guidelines2/5

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

No when-to-use guidance is provided; 'Create One' offers no context about when to choose this tool over alternatives. There is no mention of bulk creation, prerequisites, or relationship to sibling tools such as create_households_shopping_items_create_bulk or update_households_shopping_items.

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