Delete a specific household event notification from Mealie by its unique ID, removing unwanted alerts and keeping your household organized.
Delete One [DELETE /api/households/events/notifications/{item_id}]
| Name | Required | Description | Default |
|---|---|---|---|
| item_id | Yes |
Changes observed during successful MCP inspections.
v0.2.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description merely states 'Delete One' without any behavioral details. For a destructive operation like delete, it should disclose that the notification is permanently removed, any cascading effects, authorization requirements, or whether the action is reversible. No annotations are present to compensate.
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 concise, the description is under-specified. It contains only the name and HTTP method, which adds no value. Every sentence should earn its place, but here there is no informative content.
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's complexity (a simple delete with one parameter), the description is still incomplete. It does not explain the purpose, usage context, or anything about the return value (no output schema). The tool is not adequately defined for an AI agent to select and invoke 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?
The input schema has one required parameter 'item_id' with 0% description coverage. The description adds no semantic information about what 'item_id' represents (e.g., which notification, scope). The agent gains no additional insight beyond the schema.
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 'Delete One' combined with the tool name and endpoint indicates deletion of a household event notification, but it is vague and does not explicitly state what is being deleted. The purpose is implied but not clear without context.
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 usage guidelines are provided. The description does not specify when to use this tool, what prerequisites exist, or any alternatives. It fails to differentiate from sibling tools such as 'households_event_notifications_get_one' or 'households_event_notifications_update_one'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.