Update a specific ingredient unit in Mealie using its ID and the new unit data. Modify names, abbreviations, aliases, or standard conversions to keep recipe measurements consistent.
Update One [PUT /api/units/{item_id}]
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | ||
| item_id | Yes |
Changes observed during successful MCP inspections.
v0.2.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations and a minimal description, the tool fails to disclose any behavioral traits such as whether it performs a full replacement (PUT), requires authentication, or is idempotent.
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?
While extremely short, the description is under-specified and fails to convey essential information. It is concise but not useful.
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?
Given no annotations, no output schema, and a bare description, the tool is incomplete. It does not provide enough context for an agent to use it effectively.
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 description coverage is 0%, and the description adds no explanation for the parameters. The agent receives no clarity on what the 'body' parameter should contain or how 'item_id' is used.
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 'Update One' is a tautology that merely restates the purpose implied by the tool name. It does not specify that the tool updates a unit in recipes, making it vague and unhelpful.
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 is provided on when to use this tool versus alternative tools like create_one, delete_one, or get_one. The description lacks any context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.