Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Recipe details

get_recipe_details
Read-only

Fetch full recipe details by slug from Migusto, including ingredients, quantities, instructions, photos, and nutrition; use recipe search first to find the slug.

Instructions

Fetch a full Migusto recipe by slug: ingredients with quantities, step-by-step instructions, photos, nutrition. Use search_recipes first to find the slug. (Migusto is Migros' recipe site at migusto.migros.ch.)

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": {
      "slug": "<slug>"
    },
    "name": "get_recipe_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRecipe slug from search_recipes (the URL-safe name, e.g. 'marroni-aus-dem-ofen').
languageNoLanguage code: de, fr, it. Default: de.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint; the description earns credit by naming the actual external source (migusto.migros.ch), which gives the openWorld hint concrete meaning, and by listing what the response contains. It does not cover failure behavior for an unknown slug or language fallback, so it is not fully transparent.

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 sentences, front-loaded with the action and payload, then the prerequisite, then a short parenthetical identifying the site. Nothing is redundant with the schema and every clause carries information.

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 read-only, no-output-schema fetch, enumerating the returned fields is exactly the compensation needed, and the slug-provenance note closes the main usage risk. Only minor gaps remain: unknown-slug errors and whether language falls back when a translation 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% and both parameters are documented in-schema with examples and a default. The description only reinforces the slug's provenance ('from search_recipes') and says nothing about the language parameter, so it adds marginal meaning beyond the schema — baseline 3.

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?

States a specific verb and resource ('Fetch a full Migusto recipe by slug') and enumerates the payload: ingredients with quantities, instructions, photos, nutrition. The sibling split is unambiguous — search_recipes finds slugs, this one resolves a slug into a full recipe.

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 an explicit prerequisite ordering: 'Use search_recipes first to find the slug,' which routes the agent to the right sibling before calling this one. It stops short of stating when NOT to use it (e.g. that discovery-only needs should stay in search_recipes), but the sequencing covers the main misuse case.

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