Skip to main content
Glama
djwmarcx

Better Mealie MCP

by djwmarcx

delete_households_shopping_items_by_item

Delete a single shopping item from your household list using its unique ID. Keep your household shopping list organized and up to date.

Instructions

Delete One

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYes
accept-languageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations exist, so the description bears full responsibility for behavioral disclosure. It only states 'Delete One', revealing no information about side effects, authorization requirements, rate limits, or what is actually destroyed. This is insufficient for a mutation tool.

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?

At two words, the description is extremely concise but at the expense of clarity. It is under-specified and does not earn its place as a useful guide for the agent.

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 delete operation, existing output schema, and numerous sibling delete tools, the description is severely incomplete. It omits critical context about what is deleted, permissions, return values, and differentiation from other tools.

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 nothing about parameters. It does not explain the meaning of 'item_id' or 'accept-language' beyond what the schema already provides. The description must compensate for low coverage but fails to do so.

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 a tautology that merely restates the tool name without specifying what resource is being deleted. It fails to convey the tool's specific purpose beyond the name, and it does not distinguish from sibling tool 'delete_households_shopping_items'.

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 usage guidance is provided. The description does not indicate when to use this tool vs. alternatives like 'delete_households_shopping_items', nor does it mention prerequisites, context, or exclusions.

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