Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Get REWE Recipe Ingredients & Preparation Steps

rewe_get_recipe_details
Read-only

Fetch complete REWE recipe details by recipe ID, including portion yield, prep and cooking times, ingredients, step-by-step instructions, and nutrition values.

Instructions

Fetch complete REWE recipe details by recipeId: portion yield, preparation/cooking times, structured ingredients list, step-by-step instructions, and nutrition values.

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

Input Schema

NameRequiredDescriptionDefault
recipeIdYesREWE recipe ID (e.g. 'blt4aaa7361ba69f8c8').

Output Schema

NameRequiredDescriptionDefault
idYes
stepsYes
titleYes
ingredientsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes this as a safe read, and the description adds the useful note that a full detail payload (ingredients, steps, nutrition) comes back rather than a summary. It says nothing about authentication requirements, failure behavior for an invalid or stale recipe ID, or rate limits, so it goes only modestly beyond the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the key selector in the opening clause and the payload listed after. The field enumeration partially duplicates the output schema, but the sentence is short and earns its space overall.

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?

A one-parameter read tool with an output schema, so return-value documentation is not the description's burden and the schema fully documents the required ID. Nothing essential is missing for a correct call, though a pointer to rewe_search_recipes for obtaining IDs would close the last gap.

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% and the schema already supplies the ID format and an example ('blt4aaa7361ba69f8c8'). The description only restates that lookup is keyed on recipeId, adding no new meaning such as where to obtain the ID.

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

Purpose4/5

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

States a specific verb and resource ('Fetch complete REWE recipe details') and a precise scope ('by `recipeId`'), plus an enumeration of the data returned. It is clearly distinct from rewe_search_recipes by implication, but the description never names that sibling, so the differentiation is left to the reader.

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

Usage Guidelines3/5

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

The 'by `recipeId`' phrasing implies this is the ID-driven lookup step that follows a search, but there is no explicit when-to-use statement, no exclusion, and no named alternative. An agent can infer the workflow but must do so itself.

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