Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Remove from basket

remove_from_basket
DestructiveIdempotent

Remove a product from the user's Migros basket by product ID and get the updated basket back. Use it to correct or update basket contents before checkout.

Instructions

Remove a product from the user's basket. Returns the updated basket. 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": {
      "productId": "<productId>"
    },
    "name": "remove_from_basket"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdYesProduct UID to remove from the basket.
shoppingListIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already cover the safety profile (destructiveHint=true, idempotentHint=true, readOnlyHint=false), with which the description is consistent. The description adds two pieces of context that the annotations do not supply: the authentication requirement and the fact that the call returns the updated basket. It does not say what happens when the product is not present in the basket or whether an emptied basket is retained.

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?

Three short sentences, with the action front-loaded and the return value plus the prerequisite following. There is no filler or repetition.

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

Completeness3/5

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

Because there is no output schema, the description correctly states the return value and the auth requirement, and the annotations describe the safety profile. However, for a destructive mutation with an undocumented second parameter, it omits error behavior and the meaning of shoppingListId, which leaves a material gap.

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

Parameters2/5

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

Schema description coverage is only 50%: productId is documented in the schema, but shoppingListId has no description anywhere. The phrase 'the user's basket' hints at a default basket but never explains what supplying shoppingListId does or what happens if it is omitted, so the description fails to compensate for the schema gap.

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 states a specific verb ('Remove') and resource ('a product from the user's basket'), which clearly separates it from get_basket and add_to_basket. It does not explicitly distinguish itself from update_basket_quantity (e.g., setting quantity to zero), so it falls short of full sibling differentiation.

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?

The description supplies a prerequisite ('Requires authentication') but gives no explicit when-to-use or when-not-to-use guidance and never names an alternative tool. The usage is implied by the verb and by the sibling names, but the definition itself provides only that implicit guidance.

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