Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Set Default REWE Market & Service Type

rewe_set_selected_market
Idempotent

Saves the default REWE market ID, postal code, and service type to local config so later product, offer, and basket calls use the right store.

Instructions

Persist the default REWE marketId (wwIdent), zipCode (PLZ), and serviceType (PICKUP or DELIVERY) in ~/.config/rewe-mcp/store.json for subsequent product, offer, and basket calls.

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": {
      "marketId": "<marketId>"
    },
    "name": "rewe_set_selected_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city override.
zipCodeNoGerman postal code (PLZ, e.g. '50667'). Defaults to the configured zip code.
marketIdYesREWE market identifier (`wwIdent`, e.g. '840174' or '831002').
marketNameNoOptional display name override.
serviceTypeNoREWE service type ('PICKUP' for Abholservice or 'DELIVERY' for Lieferservice).

Output Schema

NameRequiredDescriptionDefault
cityNo
zipCodeYes
marketIdYes
updatedAtNo
marketNameNo
serviceTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the exact file that gets written and the fact that the values become defaults for later calls. It does not say whether an existing config is fully replaced or merged, nor whether authentication is required, which keeps it below a 5.

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 sentence that front-loads the action and the persisted fields, then closes with the downstream benefit. There is no redundant or filler wording.

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 present, return values need no explanation, and the 100%-covered schema handles parameter detail. The description covers the core write behavior and its purpose; the only gap is overwrite/merge semantics for an existing stored configuration, which matters for a persistence tool but is a minor omission.

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 is already documented in the schema, including the wwIdent and PLZ examples and the PICKUP/DELIVERY enum. The description restates the three main fields but adds no new meaning and never mentions the optional city or marketName overrides. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Persist') with a precise resource (the default marketId/zipCode/serviceType configuration) and even names the storage location (~/.config/rewe-mcp/store.json). This clearly separates it from the read-side sibling rewe_get_selected_market, which retrieves rather than persists the same state.

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

Usage Guidelines4/5

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

It states the downstream purpose explicitly ('for subsequent product, offer, and basket calls'), which tells an agent when this tool is appropriate. It stops short of naming an alternative or stating when not to call it (e.g. when the market is already set), so it is clear context without exclusions.

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