Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

List REWE Digital Store Receipts (eBons)

rewe_list_ebons
Read-only

List in-store digital receipts with timestamps, store address, total spend, and REWE Bonus earned. Set a limit to control how many eBons are returned.

Instructions

List in-store digital receipts (eBons) with timestamps, store address, total spend, and REWE Bonus earned.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of eBons to return.

Output Schema

NameRequiredDescriptionDefault
receiptsYes
ebonActiveNo
totalCountYes

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 establishes this as a safe read, so the description only needs to add context. It does add the shape of what comes back (timestamps, store address, total spend, Bonus), but says nothing about ordering, defaults, pagination behavior, or whether receipts require authentication/consent.

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 zero filler. Every clause contributes identifying or return-field information.

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 one-parameter, read-only listing tool with an output schema and readOnlyHint, the definition is nearly sufficient. Only minor gaps remain around default limit, result ordering, and the relationship to the PDF-fetch sibling.

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?

The single parameter has 100% schema description coverage with its own description and a 1-200 range, so the schema carries the meaning. The description adds nothing about limit (e.g. default value or truncation behavior), which matches the baseline 3 for a fully documented schema.

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?

The description gives a specific verb ('List') plus the exact resource ('in-store digital receipts (eBons)') and even names the fields surfaced. It is clearly distinguishable from detail-oriented siblings like rewe_get_ebon_pdf, though it does not name that sibling explicitly.

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: 'List ... receipts' signals a browsing/history call, and the contrast with a single-receipt fetch tool is inferable but never stated. There is no explicit when-to-use, when-not, or pointer to rewe_get_ebon_pdf for downloading a document.

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