Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Delete shopping list

delete_shopping_list
DestructiveIdempotent

Permanently removes a shopping list and all its items after explicit confirmation; prevents deletion of the only remaining list and requires authentication.

Instructions

Delete one of the user's shopping lists with all its items. Cannot be undone. Only deletes with confirm: true, which needs the user's explicit OK; the only remaining list is never deleted. Requires authentication.

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": {
      "shoppingListId": "<shoppingListId>"
    },
    "name": "delete_shopping_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to delete. Ask the user first: the list and its items are gone for good.
shoppingListIdYesList ID from get_shopping_lists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the safety profile is known; the description still adds real value beyond them: irreversibility ('Cannot be undone'), the confirm-gate, the need for explicit user consent, the last-list safeguard, and an authentication requirement. It does not say what the response contains on success, which is the only notable omission.

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

Conciseness4/5

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

Four short sentences, each carrying a distinct constraint, with destructiveness and the confirm gate front-loaded. Slightly fragmented in structure, but there is no filler or repetition.

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, irreversible mutation with no output schema, the description covers everything an agent needs before calling: permission requirement, confirmation protocol, irreversibility, and the protected-last-list edge case. Annotations supply the rest of the safety profile.

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

Parameters3/5

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

Schema coverage is 100%, so both parameters are already documented, including the confirm gate and the source of shoppingListId ('from get_shopping_lists'). The description only restates the confirm requirement in prose, adding emphasis rather than new semantics, so baseline 3 is appropriate.

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 opens with a specific verb and resource ('Delete one of the user's shopping lists') and immediately states the scope ('with all its items'). The verb alone separates it from create_shopping_list and rename_shopping_list, so an agent can route correctly without opening the schema.

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

Usage Guidelines4/5

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

It gives a clear operational condition: deletion only proceeds with confirm: true, which additionally requires the user's explicit OK. It also provides an exclusion ('the only remaining list is never deleted'), which is a genuine when-not constraint. No sibling alternatives are named, but none are plausible for a delete operation.

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