Skip to main content
Glama
Sign In
mealie-agent-mcp

mealie-agent-mcp

by loidolt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Remove Shopping List Items

remove_shopping_list_items
Destructive

Delete selected items or all checked-off entries from a Mealie shopping list by list ID to clear purchased products and unwanted items.

Instructions

Delete items from a shopping list: specific ids and/or all checked-off items.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "list_id": "<list_id>"
    },
    "name": "remove_shopping_list_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idYesShopping list id.
item_idsNoItem ids to delete.
all_checkedNoDelete every checked-off item on the list.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description usefully discloses that deletion can be broad (every checked-off item on the list), which raises blast-radius awareness beyond the annotations, but it omits reversibility, permission requirements, and what happens when neither selection parameter is supplied.

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

Conciseness5/5

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

A single front-loaded sentence with the target modes enumerated after the colon; nothing is redundant and the destructive scope is stated immediately.

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

Completeness4/5

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

With destructive annotations and an output schema present, the description need not explain safety or return values, and it covers the selection modes adequately. The remaining gap is the degenerate case where neither item_ids nor all_checked is provided, which an agent could plausibly encounter given both are optional.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the phrase "specific ids and/or all checked-off items" conveys union semantics — that item_ids and all_checked can be combined — which the schema itself does not state. It still leaves the empty-selection edge case (both null/false) undefined.

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

Purpose4/5

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

The description names a specific verb and resource ("Delete items from a shopping list") and scopes the target set (specific ids and/or checked-off items). This clearly separates it from siblings like add_shopping_list_items and set_shopping_list_items_checked, though it never explicitly names those alternatives.

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

Usage Guidelines3/5

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

Usage is implied: delete by explicit ids, by checked-off status, or both. There is no explicit when-to-use vs when-not guidance, and no warning that unchecking rather than deleting is handled by set_shopping_list_items_checked, which is the main routing risk among the siblings.

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