Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Download REWE eBon Receipt PDF

rewe_get_ebon_pdf
Idempotent

Download the original PDF receipt for a given eBon ID. Optionally save it to a local path; otherwise receive base64 PDF data and file size.

Instructions

Download the original PDF receipt for a given ebonId. Optionally pass savePath to write the PDF directly to disk; otherwise returns base64Pdf and sizeBytes.

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": {
      "ebonId": "<ebonId>"
    },
    "name": "rewe_get_ebon_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
ebonIdYeseBon receipt ID from rewe_list_ebons.
savePathNoOptional local file path to save the PDF directly (e.g. '~/Downloads/ebon.pdf').

Output Schema

NameRequiredDescriptionDefault
idYes
savedToNo
base64PdfNo
sizeBytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the description's job is to explain the conditional write. It does exactly that by clarifying the disk write only happens when savePath is supplied, otherwise the call is a pure retrieval. It omits overwrite behavior and filesystem permission requirements for the save path, which would have rounded this out.

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?

Two sentences, both front-loaded and free of filler. The primary action comes first and the optional mode plus return fallback follow immediately, with no redundancy against the schema.

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?

With an output schema present, the description needn't document return values, and it still usefully names base64Pdf and sizeBytes for the non-save case. For a two-parameter tool this is nearly complete; only save-path edge cases like overwriting or path expansion remain unaddressed.

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%, so both parameters are already documented, which sets the baseline at 3. The description adds some meaning by explaining the consequence of omitting savePath (base64Pdf and sizeBytes are returned instead), but contributes little on ebonId itself beyond what the schema says.

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 states a specific verb and resource — 'Download the original PDF receipt for a given ebonId' — which is clearly a retrieval action against a single receipt artifact, distinctly different from listing tools like rewe_list_ebons. It stops just short of explicitly naming the sibling it complements, leaving that differentiation to the schema reference.

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 through the two delivery modes: pass savePath to write to disk, otherwise the PDF comes back as base64. There is no explicit statement of when to prefer this over rewe_list_ebons or when each mode is appropriate, so an agent must infer that a list call should precede this one.

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