Skip to main content
Glama
djwmarcx

Better Mealie MCP

by djwmarcx

delete_groups_labels_by_item

Delete a group label by providing its item ID. Permanently removes the label from your Mealie group.

Instructions

Delete One

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYes
accept-languageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as destructiveness, auth requirements, or side effects. The description merely says 'Delete One', which is inadequate for a mutation tool with no annotation coverage.

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

Conciseness1/5

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

The description is extremely short but under-specified. It is not concise in a helpful way; essential information is missing. Every sentence should earn its place, but here the single sentence provides no value beyond the tool name.

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?

Given the complexity of a delete operation with no annotations, no param details, and an output schema (though not provided), the description is completely inadequate. It does not mention return values, success/failure conditions, or what the tool does beyond 'delete one'.

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%, and the description adds no meaning beyond the schema. Two parameters exist (item_id and accept-language), but the description provides no details about their semantics, formats, or usage.

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

Purpose2/5

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

The description 'Delete One' is minimal and essentially restates the action implied by the name 'delete_groups_labels_by_item'. It lacks a specific verb-resource combination and fails to distinguish from sibling tools like delete_groups_reports_by_item or delete_households_... It adds little clarity beyond the tool name itself.

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?

No guidance is provided on when to use this tool versus alternatives. There are many sibling delete tools (e.g., delete_groups_reports_by_item, delete_households_cookbooks_by_item), and the description offers no context for when this specific tool is appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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