Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Get Weekly REWE Store Discounts (Angebote)

rewe_get_discounts
Read-only

Fetches current weekly REWE promotional offers and discounts grouped by category, with optional filters for market, postal code, category, and result limit.

Instructions

Fetch current weekly promotional offers/discounts for a REWE market grouped by category.

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

Input Schema

NameRequiredDescriptionDefault
limitNoOptional maximum number of total offers to return.
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.
categoryIdNoOptional category ID or title substring to filter offers.

Output Schema

NameRequiredDescriptionDefault
marketIdYes
categoriesYes
handoutUrlNo
validUntilNo
totalOffersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint annotation already tells the agent this is a safe read operation, so the description's burden is lower. It adds useful scoping context (weekly cadence, per-market, category grouping), but says nothing about defaults resolution when no market or zip is supplied, result volume, or rate limits.

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?

A single front-loaded sentence with no filler; verb and scope appear immediately and nothing is repeated from the schema or annotations. It is appropriately sized for a straightforward filtered-list read.

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, full parameter documentation, and a readOnlyHint, the only meaningful gap is disambiguation from sibling discount/coupon/brochure tools. For a zero-required-parameter read tool, the definition is otherwise sufficient to invoke 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 100%, so every parameter (limit, zipCode, marketId, categoryId) is already documented upstream, including defaults and bounds. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the work.

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?

Specific verb ("Fetch") plus a well-scoped resource ("current weekly promotional offers/discounts for a REWE market") and a stated grouping behavior ("grouped by category"). It does not, however, distinguish this from the sibling rewe_search_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 Guidelines2/5

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

There is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as rewe_search_discounts, rewe_get_coupons, or rewe_get_brochure, all of which plausibly overlap. Usage is only implied by the title and the word "weekly".

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