Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Search REWE Product Catalog

rewe_search_products
Read-only

Search REWE's live supermarket assortment by product name, EAN barcode, or category for PICKUP or DELIVERY, with filters for organic, vegan, regional, and other attributes.

Instructions

Search the live REWE supermarket assortment for a market and service type (PICKUP or DELIVERY) by product name, EAN barcode, or category slug.

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_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sortNo
queryNoSearch term or EAN barcode (e.g. 'Hafermilch', '4305615100005'). Leave empty when browsing a categorySlug.
filtersNoOptional REWE attribute filters such as 'attribute=organic', 'attribute=vegan', 'attribute=regional', 'attribute=vegetarian'.
zipCodeNoGerman postal code (PLZ, e.g. '50667'). Defaults to the configured zip code.
marketIdNoREWE market identifier (wwIdent, e.g. '840174'). Defaults to the configured market.
serviceTypeNoREWE service type ('PICKUP' for Abholservice or 'DELIVERY' for Lieferservice).
categorySlugNoOptional category slug from rewe_get_shop_categories (e.g. 'obst-gemuese').
objectsPerPageNo

Output Schema

NameRequiredDescriptionDefault
pageYes
marketIdYes
productsYes
totalPagesNo
serviceTypeYes
totalProductsNo
correctedQueryNo
objectsPerPageYes

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?

readOnlyHint=true already tells the agent this is a safe read, so the description's job is smaller. It adds useful context that the assortment is 'live' and that results depend on market and service type, but it says nothing about pagination limits, result caps, or fallback behavior when no market is supplied (the schema's 'defaults to the configured market' is the only clue). Adequate but thin 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 well-formed sentence that front-loads the verb and resource before the search axes. It is dense but has no filler. Slightly more structure (e.g., separating the three lookup modes) would improve scannability.

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?

With an output schema available and only read-only annotations needed, the description covers the essential calling context: what is searched, against which market/service type, and by which key. Minor gaps remain around default market resolution and paging, but these are documented in the schema, so an agent has enough to call it correctly.

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 67%, so the schema already documents most parameters, and the description's contribution is mainly restating that query accepts a name or EAN and that category slug is a valid search axis. The PICKUP/DELIVERY mention duplicates the schema enum, and page, sort, filters, zipCode, marketId, and objectsPerPage get no added meaning from the description. Baseline 3 fits.

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?

The description gives a specific verb ('Search') plus resource ('live REWE supermarket assortment') and enumerates the three lookup modes: product name, EAN barcode, and category slug. It also scopes results to a market and service type, which separates it from catalog-wide siblings such as rewe_search_recipes or rewe_search_discounts. It stops short of naming the nearest sibling (rewe_get_product_details) as the alternative for detail lookups.

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?

Usage is implied rather than stated: an agent can infer 'use this to find products', and the schema hints that categorySlug comes from rewe_get_shop_categories. There is no explicit when-not guidance or routing to siblings like rewe_regular_products or rewe_get_product_details, so selection between the several product-oriented tools is left to inference.

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