Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Basket contents

get_basket
Read-only

Retrieve the product IDs and quantities in the user's current Migros shopping basket or shopping list, optionally for a specific list ID, then enrich items with product details.

Instructions

Fetch the items currently in the user's shopping basket (Migros calls this a shopping list). Returns product IDs and quantities; use get_product_details to enrich. If the user has several lists, use get_shopping_lists and pass shoppingListId. 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_basket"
  }
}

Input Schema

NameRequiredDescriptionDefault
shoppingListIdNoOptional shopping 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
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: it discloses the authentication requirement and the return shape (IDs plus quantities). It does not mention error behavior, pagination, or whether an empty basket is returned as empty versus an error.

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 what is fetched and returned, then routing, then the auth caveat. No redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-optional-parameter read tool with no output schema, the definition covers purpose, return payload, list-selection behavior, enrichment path, and authentication. An agent has everything needed to call it correctly on the first attempt.

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% and the schema already says the ID comes from get_shopping_lists and that omitting it uses the first list, so the description largely restates structured data. The 'if the user has several lists' phrasing does add a light trigger condition for when to look up an ID, which keeps it above a pure repeat.

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?

The description states a specific verb and resource ('Fetch the items currently in the user's shopping basket') and resolves a terminology ambiguity by noting Migros calls this a shopping list. It goes further than the name by naming the return payload (product IDs and quantities), which lets an agent distinguish it from add_to_basket, remove_from_basket, and update_basket_quantity.

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?

It routes the agent to concrete alternatives with conditions: get_product_details to enrich the results, get_shopping_lists plus shoppingListId when the user has multiple lists. It also flags the authentication prerequisite. The one gap is that no explicit when-not or refresh/caching guidance is given, but the alternative routing is clear.

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