delete_groups_reports_by_item
Delete a specific report by its item ID to remove unwanted data from your Mealie groups.
Instructions
Delete One
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| item_id | Yes | ||
| accept-language | No |
Delete a specific report by its item ID to remove unwanted data from your Mealie groups.
Delete One
| Name | Required | Description | Default |
|---|---|---|---|
| item_id | Yes | ||
| accept-language | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description does not disclose any behavioral traits such as irreversibility, 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?
Extremely short but underspecified; it is not concise but rather inadequate. Every sentence should add value, and this adds none.
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 complexity of sibling tools and lack of annotations or output schema, the description is completely insufficient for an agent to use the tool 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%, and the description adds no meaning to parameters. It does not explain the purpose of 'item_id' or 'accept-language'.
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?
Description reads 'Delete One' which is a tautology of the tool name and does not specify what resource is being deleted. It fails to convey that this tool deletes a specific group report by item ID.
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. With many sibling delete tools, there is no distinction or context for selecting this tool.
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