Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

List REWE Online Orders

rewe_list_orders
Read-only

List REWE pickup and delivery online order history, with an optional limit, to review past grocery orders.

Instructions

List REWE Abholservice (pickup) and Lieferservice (delivery) online order history.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of orders to return.

Output Schema

NameRequiredDescriptionDefault
countYes
ordersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful scope (both pickup and delivery order types) but says nothing about ordering, default page size, or pagination behavior beyond the limit parameter.

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 efficient sentence with the resource front-loaded and no redundant wording. It is appropriately sized for a simple list tool, though it leaves little room for the routing detail an agent would benefit from.

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?

For a read-only list tool with one optional parameter, an output schema, and safety annotations, the description covers what is needed to call it correctly. The only real gap is disambiguation from rewe_get_order_details, which is minor here.

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% for the single 'limit' parameter, so the schema already carries the meaning. The description adds no format, default, or ordering semantics, making the baseline 3 appropriate.

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 ('List') and resource ('online order history'), and clarifies that both Abholservice (pickup) and Lieferservice (delivery) orders are covered. It does not explicitly distinguish itself from the sibling rewe_get_order_details, so it falls 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?

Usage is only implied by the word 'history' — an agent can infer this is the bulk-listing tool rather than the single-order detail tool, but no when-to-use, exclusions, or alternatives are named despite rewe_get_order_details being a close sibling.

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