Skip to main content
Glama
djwmarcx

Better Mealie MCP

by djwmarcx

patch_recipes_by_slug

Update a recipe by providing its slug and the fields to modify. Patch recipe data such as name, ingredients, instructions, and nutrition using the existing slug.

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
Behavior1/5

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

No annotations provided, and the description discloses no behavioral traits such as error handling, partial vs full update, authentication needs, or rate limits. The description is completely silent on these aspects.

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 only one sentence, making it concise but too brief to be useful. It lacks structure and essential details, appearing under-specified rather than efficient.

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 the complexity of 35 parameters and no output schema, the description is completely inadequate. It does not explain which fields can be updated, how to identify the recipe, or what the response looks like.

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 description only uses 'data' generically, adding no meaning beyond the input schema. With 35 parameters and only 3% schema description coverage, the description should compensate but does not.

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 it updates a recipe using an existing slug and data. The verb 'updates' and resource 'recipe' are explicit, but it does not differentiate from sibling tools like 'patch_recipes' or 'update_recipes_by_slug'.

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 guidance on when to use this tool versus alternatives. No prerequisites, exclusions, or conditions are mentioned. The description lacks any usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/djwmarcx/better-mealie-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server