Skip to main content
Glama
Sign In
mealie-mcp

mealie-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Remove shopping list items

delete_shopping_list_items
DestructiveIdempotent

Permanently remove shopping list items with a two-step confirmation token.

Instructions

Removes items from a shopping list for good. To merely tick something off, use update_shopping_list_items with checked=true. Requires confirmation: call once to receive a token, then again with that token.

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": {
      "item_ids": "<item_ids>"
    },
    "name": "delete_shopping_list_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idsYesItem UUIDs from get_shopping_list
confirm_tokenNoConfirmation token from a previous call of this tool with the same arguments. Omit on the first call.

Output Schema

NameRequiredDescriptionDefault
truncatedNoPresent only when entries were dropped to fit the budget.
removed_countYes
removed_item_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / confirm_token / maxLength
      Added value: +512
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "properties": {
+    "removed_count": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "removed_item_ids": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "truncated": {
+      "additionalProperties": true,
+      "description": "Present only when entries were dropped to fit the budget.",
+      "properties": {
+        "follow_up": {
+          "type": "string"
+        },
+        "reason": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "reason",
+        "follow_up"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "removed_count",
+    "removed_item_ids"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds the crucial two-step confirmation token flow, clarifying that deletion is permanent and requires explicit confirmation. No contradiction with annotations.

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?

Two sentences with no filler; the core purpose is front-loaded, and the alternative tool and confirmation requirement are stated clearly. Every word earns its place.

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

Completeness5/5

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

For a destructive operation with a two-step flow, the description covers purpose, alternative, and confirmation procedure. The schema describes the item_ids origin (from get_shopping_list) and the output schema exists, so no return value explanation needed.

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?

Both parameters have descriptions in the schema (100% coverage). The description adds the semantic meaning of confirm_token: 'call once to receive a token, then again with that token,' which clarifies the required sequence beyond the schema's generic description.

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

Purpose5/5

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

The description uses a specific verb 'Removes' and a specific resource 'items from a shopping list', and explicitly contrasts with the sibling update_shopping_list_items for ticking items off. This clearly differentiates it from other list tools.

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

Usage Guidelines5/5

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

It explicitly directs when not to use this tool ('To merely tick something off, use update_shopping_list_items with checked=true') and explains the required two-step confirmation process, giving clear guidance on invocation.

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