Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Search Weekly REWE Discounts by Keyword

rewe_search_discounts
Read-only

Search current weekly REWE stationary offers by product, brand, or category keyword to find discounts at a selected market.

Instructions

Search current weekly stationary offers at the selected REWE market by product name, brand, or category keyword.

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": {
      "query": "<query>"
    },
    "name": "rewe_search_discounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesKeyword to match against weekly offers (e.g. 'Milch', 'Haribo', 'Kaffee').
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.

Output Schema

NameRequiredDescriptionDefault
queryYes
offersYes
marketIdYes
validUntilNo
totalMatchesYes

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. The description adds useful scope ('current weekly', 'selected REWE market'), but says nothing about result ordering, pagination, or what happens when the keyword matches nothing.

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 scope qualifiers come before the matching criteria. Slightly terse given the tool has four parameters.

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?

An output schema exists, so return values need not be described, and the market-scoping defaults are covered by the schema. What remains missing is guidance on choosing this over rewe_get_discounts and on result limits.

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 75%, so most parameters are already documented. The description adds meaning to query by naming the match dimensions (name, brand, category), but says nothing about limit or how zipCode/marketId override the configured defaults beyond what the schema states.

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 resource (current weekly stationary offers) plus the matching dimensions (product name, brand, category keyword). It does not distinguish itself from the sibling rewe_get_discounts, so an agent cannot tell from the text alone which of the two to pick.

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 by 'by product name, brand, or category keyword' and by the market scoping, but there is no explicit when-to-use/when-not guidance and no mention of the obvious alternative rewe_get_discounts for browsing all offers.

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