Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Get Available REWE Pickup/Delivery Timeslots

rewe_get_timeslots
Read-only

Retrieve available REWE pickup or delivery checkout timeslots and service fees for the current basket and market, with optional ZIP code and service type filters.

Instructions

List available Abholservice (pickup) or Lieferservice (delivery) checkout timeslots and service fees for the current basket and market.

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

Input Schema

NameRequiredDescriptionDefault
zipCodeNoGerman postal code (PLZ, e.g. '50667'). Defaults to the configured zip code.
basketIdNo
marketIdNoREWE market identifier (wwIdent, e.g. '840174'). Defaults to the configured market.
serviceTypeNoREWE service type ('PICKUP' for Abholservice or 'DELIVERY' for Lieferservice).

Output Schema

NameRequiredDescriptionDefault
countYes
timeslotsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes this is a safe read, and the description is consistent with that by using 'List'. It adds genuine context beyond the annotation — results depend on the current basket and market and include service fees — but says nothing about empty results, market/basket prerequisites, 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?

One sentence, front-loaded with the verb and resource, with the German service names glossed by their English equivalents. Nothing is redundant or padding.

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 explained, and the read-only annotation covers the safety profile. For a zero-required-parameter read tool this is nearly complete; only the dependency on an existing basket/market selection and the undefined basketId are left implicit.

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% (zipCode, marketId, and serviceType are documented with examples and enum values), so the baseline is 3. The description's mention of 'current basket' and pickup/delivery loosely maps to basketId and serviceType but adds no format, default, or precedence detail beyond the schema; basketId remains entirely undocumented in the schema.

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 ('List') plus a precise resource ('Abholservice or Lieferservice checkout timeslots and service fees'), and scopes it to 'the current basket and market'. No sibling tool covers timeslots, so an agent can distinguish it immediately from basket, market, or product tools.

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 phrase 'for the current basket and market', which tells the agent this belongs to a checkout-planning flow, but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer that it should be called after a basket exists.

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