Skip to main content
Glama
djwmarcx

Better Mealie MCP

by djwmarcx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Patch Recipes By Slug

patch_recipes_by_slug

Update an existing recipe by its slug with new data. Provide the slug and fields to modify to apply changes.

Instructions

Updates a recipe by existing slug and data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
slugNo
tagsNo
imageNo
notesNo
toolsNo
assetsNo
extrasNo
orgURLNo
ratingNo
userIdNo
groupIdNo
commentsNo
cookTimeNo
lastMadeNo
prepTimeNo
settingsNo
createdAtNo
dateAddedNo
nutritionNo
totalTimeNo
update_atNo
slug__pathYes(Path parameter)
dateUpdatedNo
descriptionNo
householdIdNo
performTimeNo
recipeYieldNo
recipeCategoryNo
recipeServingsNo
accept-languageNo
recipeIngredientNo
recipeInstructionsNo
recipeYieldQuantityNo

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

C2.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals nothing about side effects, error handling (e.g., what happens if slug is not found), whether the operation is a partial patch or full replacement, or any permission requirements. For a mutation tool, this is a severe 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?

The description is a single, terse sentence which is concise but not structured meaningfully for a tool of this complexity. It front-loads the action but gives no breakdown of parameters, examples, or behavior. The brevity is appropriate only for trivially simple tools, which this clearly is not.

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?

The tool has 35 parameters, no output schema, no annotations, and a near-empty schema description. The description does not provide any of the missing context: how to structure the request body, which fields are editable, what the response contains, or error scenarios. An agent cannot safely and correctly invoke this tool based on the definition provided.

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?

The schema description coverage is only 3% (just the slug path parameter), and the description adds no parameter information whatsoever. With 35 parameters, almost all undocumented, the agent has no way to know what shape the 'data' payload should take, which fields are required vs optional, or how nested structures like ingredients or instructions should be provided. This is a critical failing.

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

Purpose4/5

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

The description clearly states a specific verb (Updates) and resource (recipe) and identifies the key parameter (existing slug). It is not a tautology and gives the agent a basic sense of what the tool does. However, it does not differentiate this from sibling tools like update_recipes_by_slug or patch_recipes, which likely have similar purposes but may differ in semantics (partial vs full update).

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?

There is no guidance on when to use this tool versus the many closely related patch/update tools in the sibling list. No mention of partial vs full update, prerequisites, or scenarios where an alternative like update_recipes_by_slug should be preferred. The agent is left to guess the selection criteria.

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