Skip to main content
Glama
djwmarcx

Better Mealie MCP

by djwmarcx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Create Households Shopping Items Create Bulk

create_households_shopping_items_create_bulk

Create Many

Instructions

Create Many

Input Schema

NameRequiredDescriptionDefault
bodyYes
accept-languageNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+    }
+  ]
+}
  2. 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"
+]
  3. 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"
+}
  4. 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"
+}
  5. 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 carries the full burden, yet it discloses nothing: not that this is a write, not atomicity/partial-failure behavior for a bulk insert, not auth or permission requirements, not whether items must belong to an existing shopping list.

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, front-loading nothing useful. It is short but by under-specification, not efficiency; nothing an agent needs 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?

A bulk mutation with a complex nested input and no annotations needs substantially more disclosure. Even with an output schema present, the description leaves the submission contract, failure semantics, and list-scoping requirement entirely unexplained.

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 there are two parameters, one of them a deeply nested ShoppingListItemCreate array. The description adds no meaning for body (the list of items to create) or for accept-language, so the required body shape is entirely undocumented.

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?

"Create Many" merely restates the bulk aspect of the name without naming the resource (shopping list items) or where they are created. The agent must infer from the tool name and the schema's ShoppingListItemCreate definition that this is a bulk item-creation endpoint.

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 when-to-use, no exclusions, no distinction from the single-item sibling create_households_shopping_items or create_households_shopping_lists_by_item_recipe. There is no guidance at all.

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