Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Products for a recipe

get_recipe_products
Read-only

Fetch Migros products Migusto suggests for a recipe by recipe ID, including name, price, and UID for basket adds, to bridge recipe ingredients to shopping.

Instructions

Fetch the Migros products Migusto suggests for a recipe, with name, price and the product UID that add_to_basket takes. Bridges recipes to shopping. Use the recipe ID from search_recipes (NOT the slug). Ingredients without a suggested product: use search_products.

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": {
      "recipeId": "<recipeId>"
    },
    "name": "get_recipe_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax products to return. Default: 50.
offsetNo0-based offset for pagination.
languageNoLanguage code: de, fr, it. Default: de.
recipeIdYesNumeric recipe id from search_recipes (e.g. '39632'). NOT the slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.5/5.0
Behavior4/5

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

Read-only access is already covered by readOnlyHint=true and openWorldHint=true. Beyond that, the description discloses what the response contains and that the returned product UID is the identifier add_to_basket expects, which is genuinely useful chaining context. It does not mention result limits or behavior for recipes with no suggested products.

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?

Four short sentences, each front-loaded with a distinct fact: purpose, return shape and downstream use, ID requirement, and the fallback. There is no filler.

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?

The tool takes four parameters and has no output schema, which puts the burden on the description to explain return values; the description does that and also explains how the tool fits between recipe search and basket insertion. Nothing essential is missing.

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 the schema already documents limit, offset, language, and recipeId, including the 'NOT the slug' note. The description restates the recipeId constraint but adds no format or semantics beyond the schema. This is the expected 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.

Purpose5/5

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

The description gives a specific verb (Fetch) and a specific resource (Migros products Migusto suggests for a recipe), and it identifies the exact fields returned: name, price, and product UID. This clearly distinguishes it from search_recipes and search_products.

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

Usage Guidelines5/5

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

The description names the upstream tool, search_recipes, and warns against passing a slug instead of the numeric ID. It also gives an explicit fallback: ingredients without a suggested product should go to search_products.

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