Skip to main content
Glama
djwmarcx

Better Mealie MCP

Delete Groups Reports By Item

delete_groups_reports_by_item

Delete a specific group report using its item ID. Helps keep household data clean by removing outdated or unwanted reports.

Instructions

Delete One

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYes
accept-languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.20.1

TDQS

D1.3/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Delete One' merely restates the destructive nature already evident from the tool name and gives no information about irreversibility, cascading effects, permissions, or response behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While the description is short and front-loaded, it is under-specified rather than appropriately concise. 'Delete One' is too little content to serve as a meaningful tool description, akin to a placeholder.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, but with no annotations, no output schema, and no parameter descriptions, the description must compensate. It fails to explain what resource is deleted, how item_id is used, or whether the delete is restricted by group or household context. This is inadequate for an agent to invoke the tool confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate by explaining what item_id refers to and what the optional accept-language parameter does. It does neither, leaving both parameters entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete One' provides a verb but no resource, making it impossible to tell what is being deleted. It does not state 'report', 'groups report', or any identifying object, and it does not distinguish this tool from the many other delete_*_by_item siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to use this tool versus the many similar delete tools, such as delete_groups_labels_by_item or delete_recipes_timeline_events_by_item. The name suggests deletion by item_id, but the description does not state any context, prerequisites, or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools