Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Search REWE Recipes

rewe_search_recipes
Read-only

Search REWE recipes by keyword, difficulty, collection, or tags to find dishes that match your meal preferences and dietary needs.

Instructions

Search REWE recipe database by keyword, difficulty, collection, or tags.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
tagsNoOptional lowercase recipe tags (e.g. ['vegan', 'gesund']).
sortingNo
collectionNoOptional recipe collection (e.g. 'Vegetarisch', 'Fleisch', 'Fisch', 'Backen').
difficultyNoOptional difficulty filter ('1'/'easy', '2'/'medium', '3'/'hard').
searchTermNoKeyword or dish name (e.g. 'Lachs', 'Pasta', 'Curry').
objectsPerPageNo

Output Schema

NameRequiredDescriptionDefault
recipesYes
totalCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds that the search targets a recipe database across several facets, but says nothing about pagination behavior, default result volume, default sort order, or what a result contains — the output schema covers returns, but sort/paging behavior is unaddressed.

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 no filler; the verb, resource, and facets all land immediately. It is efficient but thin — there is no second sentence to carry the usage or behavioral context this tool needs.

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

Completeness3/5

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

With seven optional parameters, no required fields, and an output schema present, the definition covers the happy path adequately. It falls short on sorting semantics, pagination guidance, and how the filters interact, which matter for an all-optional faceted search.

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 57%, and the description covers four of seven parameters (keyword, difficulty, collection, tags) at a level already matched or exceeded by the schema's own field descriptions. Page, sorting, and objectsPerPage get no mention in either place, so meaning is not added beyond the schema.

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 (search) and a specific resource (REWE recipe database), and names the four filter dimensions. It implicitly distinguishes itself from rewe_search_products/rewe_search_discounts by scoping to recipes, but never makes that contrast explicit.

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

Usage Guidelines2/5

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

No guidance on when to use this vs. rewe_get_recipe_details or rewe_get_recipe_popular_terms, and no note on whether filters combine or whether the call works with no arguments at all. The agent must infer usage from the name alone.

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