Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Plan REWE Grocery Trip with Current Offers & Coupons

rewe_plan_grocery_trip
Read-only

Cross-reference regular REWE products and extra shopping list items against current weekly stationary discounts and Bonus coupons to find matches and plan a grocery trip.

Instructions

Cross-reference your regular REWE products and extra shopping list items against current weekly stationary discounts and REWE Bonus coupons.

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

Input Schema

NameRequiredDescriptionDefault
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.
maxOrdersNo
extraItemsNoAdditional shopping list items to match against active offers and Bonus coupons.
minPurchasesNo
onlyDiscountedNoIf true, omit regular items that have no current offer or coupon match.

Output Schema

NameRequiredDescriptionDefault
noteNo
zipCodeYes
marketIdYes
serviceTypeYes
minPurchasesYes
dueForRestockYes
offersCheckedYes
otherRegularsYes
couponsCheckedYes
ordersAnalyzedYes
discountedRegularsYes
requestedItemDealsYes
unactivatedMatchingCouponsYes

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?

Annotations already declare readOnlyHint=true, and the description is consistent with a safe read (no writes, no state change). It adds useful scope context about which data sources are combined (regular products, extra items, weekly discounts, Bonus coupons), but says nothing about how matching is ranked, whether it is market-scoped, or any auth requirement. Adequate, not rich.

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?

One front-loaded sentence with zero filler. It is dense with stacked qualifiers ('current weekly stationary discounts'), which slightly reduces scannability, but nothing is redundant or wasted.

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?

The description conveys what the tool produces (a cross-referenced plan) and an output schema covers return values. However, for a 6-parameter composite tool with defaults for zipCode/marketId and matching thresholds, it omits how the inputs shape results, leaving meaningful gaps around scoping and match-count behavior.

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 67%, so baseline is around 3. The description clarifies that extraItems are matched against offers and coupons, and the 'regular REWE products' phrasing hints at how regular-item selection works, but the thresholds governed by minPurchases and maxOrders are left undocumented in both schema and description.

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?

A specific verb ('Cross-reference') applied to concrete resources: the user's regular products plus extra list items, matched against weekly stationary discounts and Bonus coupons. This clearly distinguishes a composite planning tool from raw-fetch siblings like rewe_get_discounts or rewe_get_coupons, though it never names them.

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 the planning framing (cross-referencing a whole trip), so an agent can infer this is the aggregate/decision tool rather than a single-source lookup. No explicit when-to-use statement, no when-not, and no named alternative such as rewe_search_discounts for targeted queries.

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