Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Add to basket

add_to_basket
DestructiveIdempotent

Adds a product to a Migros basket by product ID and sets its target quantity, replacing any existing quantity; check the basket first to add on top.

Instructions

Add a product to the user's basket. If it is already there, its quantity is replaced by the new one, not added to (check get_basket first to add on top). 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": "add_to_basket"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityNoTarget quantity. Defaults to 1. REPLACES existing quantity, not increment.
productIdYesProduct UID from search_products (e.g. '100049709').
shoppingListIdNoOptional list ID from get_shopping_lists; omit to use the first list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.1/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true but say nothing about why; the description explains the core behavior, namely that quantity is replaced rather than incremented, which is what a reader needs in order to understand the destructive semantics. It also discloses the auth requirement and that the updated basket is returned.

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?

Three short sentences, with the replacement caveat placed immediately after the action instead of buried. The parenthetical correction is slightly awkward but earns its place by preventing the most likely mistake.

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 three-parameter mutation with no output schema, the description covers the mutation semantics, the auth prerequisite, and the return shape. The only gap is which list gets used when shoppingListId is omitted: that is covered in the schema but not in the description.

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 productId, quantity, and shoppingListId are already documented in detail, including the fact that quantity replaces rather than increments. The description reinforces that nuance but adds no format, range, or sourcing detail beyond the schema. A 3 is the baseline when the schema does the work.

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 ('Add a product to the user's basket') with a clear scope. However, it never addresses how it differs from the very similar sibling update_basket_quantity, which is exactly what its replacement semantics make ambiguous.

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?

Gives explicit conditional guidance: check get_basket first if the intent is to add on top of an existing quantity. It also notes the authentication prerequisite. It stops short of naming update_basket_quantity as the alternative when the goal is to change only a quantity, leaving one obvious inference unmade.

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