Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Check REWE Pickup & Delivery Availability for Zip Code

rewe_get_service_portfolio
Read-only

Check whether REWE delivery or pickup is available for a German postal code and list matching market IDs to plan grocery orders.

Instructions

Check whether REWE Lieferservice (delivery) and REWE Abholservice (pickup) are available for a German postal code (PLZ), and list matching market IDs.

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

Input Schema

NameRequiredDescriptionDefault
zipCodeNoGerman postal code (PLZ, e.g. '50667'). Defaults to the configured zip code.

Output Schema

NameRequiredDescriptionDefault
zipCodeYes
pickupMarketsYes
customerZipCodeNo
deliveryMarketIdNo
availableServiceTypesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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. Beyond that, the description adds two useful behaviors: that it covers both delivery and pickup service types, and that it returns matching market IDs. It says nothing about authentication requirements, whether an unserviceable PLZ yields an empty result or an error, or any rate limits, so the disclosure is moderate rather than rich.

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?

One sentence, front-loaded with the core action and resource, ending with the return content. No filler, no repetition, nothing an agent must skip past.

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?

Given a single optional parameter, an output schema, and a readOnly annotation, the description supplies everything essential: what is checked, for what locale, and what comes back. A note on the empty/negative result shape would make it fully complete, but that is a minor gap.

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% and the single zipCode parameter already documents format and the configured-default fallback, so the schema carries the burden. The description's only added nuance is 'German postal code (PLZ)', which largely restates the schema. Baseline 3 applies.

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 and resource: check availability of REWE Lieferservice (delivery) and Abholservice (pickup) for a German PLZ, returning matching market IDs. The two service types and the market-ID output make the purpose unambiguous. It does not explicitly distinguish itself from nearby tools such as rewe_search_markets or rewe_get_market_details, which keeps it from a 5.

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?

The usage context is implied clearly enough — this is the tool for 'can I get REWE delivery/pickup at this postal code'. However, there is no explicit when-not guidance and no named alternative for related needs (e.g., looking up details of a specific market), so the agent must infer routing itself.

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