Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Get REWE Online Order Details

rewe_get_order_details
Read-only

Fetch a REWE online order's full line-item breakdown, quantities, prices, and timeslot details by order ID to review or verify a purchase.

Instructions

Fetch full line-item breakdown, quantities, prices, and timeslot details for a REWE online order.

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": {
      "orderId": "<orderId>"
    },
    "name": "rewe_get_order_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYesOnline order ID from rewe_list_orders.

Output Schema

NameRequiredDescriptionDefault
idYes
itemsYes
statusNo
createdAtNo
totalPriceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read, so the bar is lower. The description does add useful content about what comes back (line-item breakdown, quantities, prices, timeslots), but says nothing about pagination, limits, or errors for an unknown/expired order ID.

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 front-loaded sentence naming the verb, the resource, and the returned fields, with no filler. Nothing in it is redundant with the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 no prose explanation, and the readOnly annotation covers the safety profile. For a one-parameter lookup tool the description supplies everything an agent needs to select and invoke it correctly.

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?

Only one parameter exists and schema description coverage is 100%, with the schema itself noting the orderId comes from rewe_list_orders. The description adds no format, length, or validation semantics beyond the schema, so 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 (fetch) and resource (REWE online order details) plus the exact fields surfaced: line items, quantities, prices, timeslot. This clearly distinguishes it from rewe_list_orders, which supplies the IDs. It stops short of naming siblings explicitly, so a 4 rather than 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?

Usage is only implied: an agent can infer it is the detail step after rewe_list_orders, but the description never states when to call this versus rewe_get_basket or rewe_get_timeslots, nor any precondition such as requiring a valid order ID from a prior listing. No exclusions or alternatives are given.

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