Skip to main content
Glama
migros-mcp

migros-mcp

by herp75

Search Migusto recipes

search_recipes
Read-only

Search Migusto recipes by free-text query or ingredients to get recipe IDs, titles, cooking time, and ratings for meal planning.

Instructions

Search Migusto (Migros' recipe site) by free-text query and/or ingredients. Returns recipe id, slug, title, cooking time, rating. Use get_recipe_details for full info or get_recipe_products to get Migros product UIDs to add to the basket.

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": "search_recipes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax recipes to return. Default: 20.
queryNoFree-text search term, e.g. 'pasta carbonara'.
offsetNo0-based offset for pagination.
languageNoLanguage code: de, fr, it. Default: de.
ingredientsNoFilter to recipes that use these ingredients.

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?

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds useful value by enumerating the returned fields (id, slug, title, cooking time, rating) even though no output schema exists. It stops short of anything about empty-result behavior or result ordering, so it is strong but not exhaustive.

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, zero filler, with the identification and search scope front-loaded ahead of the sibling routing. Every clause carries information an agent needs.

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 read-only, five-optional-parameter search tool with no output schema, the description covers purpose, return shape, and routing to follow-up tools. Nothing needed to invoke it correctly 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 description coverage is 100%, so every parameter (limit, query, offset, language, ingredients) is already documented in the schema. The description only reinforces the query/ingredients combination semantics and adds no format or syntax detail beyond that, which is the baseline 3 case.

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 ('Search Migusto ... by free-text query and/or ingredients') and explicitly distinguishes the result fields (id, slug, title, cooking time, rating). An agent can tell this apart from get_recipe_details and get_recipe_products without opening any schema.

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?

Explicitly routes the agent: use get_recipe_details for full info, get_recipe_products to get Migros product UIDs for the basket. That names the alternatives and the condition that selects each, so no inference is required.

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