Update an existing recipe in Mealie using its slug and new data. Modify ingredients, steps, servings, and other fields to keep recipes accurate and current.
Update One [PUT /api/recipes/{slug}] Updates a recipe by existing slug and data.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | ||
| slug | Yes |
Changes observed during successful MCP inspections.
v0.2.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description must carry the burden. It fails to disclose whether this is a full replacement (PUT) or partial update, nor mentions idempotency, permissions, or side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise (two lines) and front-loaded with the HTTP method. However, it sacrifices important details for brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations, output schema, and a complex input schema, the description leaves many aspects unexplained. An agent would struggle to use this tool correctly without additional documentation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, yet the description only mentions 'slug and data' without explaining the structure or significance of the body parameter. The body is a complex nested object but lacks any description of its fields.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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. It distinguishes from siblings like create, delete, and get operations, though it doesn't explicitly differentiate from patch_one or update_many.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 like patch_one or recipe_crud_update_many. No prerequisites or context for usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.