Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Get Current REWE Basket

rewe_get_basket
Idempotent

Fetch or initialize the active REWE Pickup or Delivery basket for a configured market and return items, totals, version, and minimum order threshold status.

Instructions

Fetch or initialize the active REWE Pickup or Delivery basket for the configured market and return items, totals, version, and minimum order threshold status.

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

Input Schema

NameRequiredDescriptionDefault
zipCodeNoGerman postal code (PLZ, e.g. '50667'). Defaults to the configured zip code.
basketIdNoOptional existing basket UUID.
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
idYes
itemsYes
versionNo
zipCodeYes
marketIdYes
itemCountYes
totalPriceNo
serviceTypeYes
totalQuantityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations declare readOnlyHint=false with idempotentHint=true, and the description explains why: the call may initialize a new basket as a side effect. That is genuinely useful context beyond the annotations. It still omits auth requirements and conflict behavior when basketId and marketId/zipCode disagree.

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?

A single dense sentence with the core action and scope front-loaded and no filler. The trailing enumeration of return fields is slightly compressed but still readable.

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 spelled out, and all four parameters are documented in schema. The description covers the main behavioral wrinkle (initialization). Missing only auth/precondition and market-selection context for a stateful, non-read-only tool.

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 100% with per-parameter descriptions and an enum for serviceType, so the schema already carries the parameter meaning. The description adds nothing about precedence between basketId, marketId, and zipCode beyond the defaults already documented. 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?

Specific verbs ('Fetch or initialize') plus a precise resource ('active REWE Pickup or Delivery basket') scoped to the configured market, and it names what comes back (items, totals, version, threshold status). It does not explicitly distinguish itself from siblings such as rewe_set_basket_item, so it stops short of 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 dual verb 'Fetch or initialize' implies the usage context: call it to obtain the current basket, creating one when none exists. However, there is no explicit when-not guidance, no statement of preconditions (auth, selected market), and no pointer to the mutation sibling for adding items.

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