Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Your shopping lists

get_shopping_lists
Read-only

Retrieve a user's Migros shopping lists with IDs and names to identify and pass the correct shoppingListId to basket tools. Requires authentication.

Instructions

List the user's Migros shopping lists (id and name). Call this when the user mentions a specific list or has several: pass the chosen shoppingListId to the basket tools. Requires authentication.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_shopping_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the read-only and open-world profile, and the description adds a genuinely operational constraint the agent must handle: it requires authentication. It also declares the returned shape (id and name). It does not mention behavior for an empty list or many lists, which is the remaining gap.

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?

Two short sentences, front-loaded with the identification of the resource, followed by the usage rule and the auth note. Every clause carries information; nothing is repeated from annotations or schema.

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 zero-parameter, read-only tool with no output schema, the definition supplies resource identity, return fields, trigger condition, auth requirement, and the handoff target. Only edge-case behavior (no lists, many lists) is unaddressed, which is minor at this complexity.

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

Parameters4/5

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

The tool takes no parameters, so there is nothing for the description to document; baseline for a zero-parameter tool applies. The mention of shoppingListId is not a parameter of this tool but usefully tells the agent where the value comes from and where it goes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ("List the user's Migros shopping lists") and even specifies the returned fields (id and name), which distinguishes it immediately from the create/delete/rename siblings. An agent knows exactly what this returns without opening a schema.

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 a clear triggering condition ("when the user mentions a specific list or has several") and states the downstream action: pass the chosen shoppingListId to the basket tools. It stops short of naming a sibling alternative or a when-not condition, so it is strong context without full routing guidance.

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