Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Rename shopping list

rename_shopping_list
DestructiveIdempotent

Change the name of an existing Migros shopping list by replacing its old name with a new one; requires the list ID and a signed-in account.

Instructions

Rename one of the user's shopping lists. The old name is replaced. 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": "<name>"
    },
    "name": "rename_shopping_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe new name.
shoppingListIdYesList ID from get_shopping_lists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description still adds useful specifics beyond that: the old name is explicitly replaced (what is lost) and authentication is required. It does not describe error behavior for an invalid ID, keeping it below a 5.

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 core action front-loaded and no wasted wording. The replacement semantics and auth requirement are stated compactly.

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 simple two-parameter mutation with rich annotations and full schema coverage, the description covers everything an agent needs to invoke it correctly. Only edge-case behavior (nonexistent list, permission failure) is left unstated.

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% — both shoppingListId and name are documented in the schema, including the min/max length and the hint to source the ID from get_shopping_lists. The description adds no additional parameter meaning, so the baseline 3 applies.

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 names a specific verb and resource ('Rename one of the user's shopping lists'), which clearly separates it from create_shopping_list and delete_shopping_list. It stops short of explicitly contrasting with those siblings, but the operation is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over create_shopping_list or delete_shopping_list, and no mention of what to do if the list does not exist. 'Requires authentication' is a prerequisite rather than usage guidance.

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