Update an existing food item's properties such as name, aliases, plural name, or description using the item's unique ID.
Update One
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ||
| name | Yes | ||
| extras | No | ||
| aliases | No | ||
| item_id | Yes | ||
| labelId | No | ||
| pluralName | No | ||
| description | No | ||
| accept-language | No | ||
| householdsWithIngredientFood | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, and the description fails to disclose any behavioral traits (e.g., permissions, mutability, side effects). The description carries the full burden but offers nothing.
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 the description is short, it is underspecified rather than concise. It fails to convey necessary information in its single phrase.
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 the tool has 10 parameters, a complex schema, and an output schema, the description is completely inadequate for an agent to select and invoke it correctly.
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%, yet the description adds no meaning beyond parameter names. It does not explain the role of parameters like 'extras', 'aliases', or the required 'item_id' and 'name'.
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 restates the name without specifying what is being updated. It lacks a verb+resource structure and does not distinguish from sibling tools like 'update_foods_merge'.
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 alternatives such as 'update_foods_merge' or other update tools in the sibling list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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