Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Note on a list item

set_item_note
DestructiveIdempotent

Set or replace a note on an item already in a shopping list while keeping its quantity; requires authentication.

Instructions

Set the note of an item already in a shopping list (e.g. 'laktosefrei'), keeping its quantity. Replaces an earlier note. 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>",
      "note": "<note>"
    },
    "name": "set_item_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesThe note, e.g. 'laktosefrei' or 'die grosse Packung'.
productIdYesProduct UID of an item already in the list.
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/5.0
Behavior4/5

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

The description restates the mutation semantics in plain language ('Replaces an earlier note') and adds an auth requirement not present in the annotations, which otherwise carry destructiveHint=true and idempotentHint=true. It does not cover failure behavior (e.g. product not in list) but does disclose the key side effect and the non-side-effect on quantity.

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, front-loaded with the action and scope, followed by state-change semantics and the auth prerequisite. Nothing is wasted or repeated.

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 3-parameter mutation with full schema coverage and rich annotations and no output schema, the description covers scope, side effect, and auth. A mention of what happens when the item or list is not found would make it complete.

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 description coverage is 100%, including examples for note and the explicit fallback behavior for shoppingListId, so the schema does the heavy lifting. The description adds only the note example and the 'keeping its quantity' clarification, which is a baseline-level contribution.

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 (set) and resource (note of a list item), plus scope qualifiers ('item already in a shopping list', 'keeping its quantity') that separate it from basket-add siblings. It does not name any sibling explicitly, so it falls just short of full differentiation.

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?

Usage context is clear: the item must already be in a list, the call replaces a prior note, and quantity is untouched. The authentication prerequisite is stated. There is no explicit pointer to alternatives such as add_to_basket or the authenticate tool for obtaining credentials.

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