Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Set basket quantity

update_basket_quantity
DestructiveIdempotent

Sets an exact quantity for a product in a Migros basket; set quantity to 0 to remove the item and return the updated basket.

Instructions

Set an item's exact quantity in the basket. quantity=0 removes the item. 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>",
      "quantity": "<quantity>"
    },
    "name": "update_basket_quantity"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityYesExact target quantity. 0 removes the item.
productIdYesProduct UID.
shoppingListIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true and readOnly=false, so the safety profile is covered. The description adds genuinely new context: an authentication requirement, the return value ('Returns the updated basket'), and confirmation that zero quantity is the deletion path – consistent with destructiveHint=true.

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, front-loaded with the action and side effect, followed by return value and auth. No wasted wording; the only omission is that the sentences are terse to the point of skipping the shoppingListId nuance.

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?

For a mutation tool with no output schema, the description covers the key behavioral facts an agent needs: auth requirement, return shape, and destruction semantics via quantity=0. Remaining gap is the unspecified role of shoppingListId when a user has multiple baskets.

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 67%, and the description only restates the quantity semantics already present in the schema ('0 removes the item'). The third parameter, shoppingListId, is never explained in the schema or the description, leaving ambiguity about which basket is targeted when multiple lists exist.

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?

States a specific verb and resource: 'Set an item's exact quantity in the basket.' This distinguishes it from add_to_basket (incremental) and remove_from_basket in effect, though it never names those siblings explicitly.

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 line 'quantity=0 removes the item' gives an implied usage path for removal, but there is no explicit guidance on when to use this versus add_to_basket for increments or remove_from_basket for full removal. Context is inferable from sibling names, not stated.

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