Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Get REWE Bonus Balance & Loyalty Overview

rewe_get_bonus
Read-only

Retrieve your REWE Bonus euro credit balance, loyalty points, tier status, and active article missions to track rewards and see what coupons or missions are available.

Instructions

Fetch your REWE Bonus euro credit balance, loyalty points overview, tier status, and active article missions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
statusTierNo
balanceCentsNo
balanceEurosNo
loyaltyPointsNo
missionsCountNo

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 non-mutating read, so the description's burden is reduced. It adds the four data categories returned, but says nothing about auth requirements, whether a missing loyalty account yields an error or empty result, or any rate/scope constraints; the presence of an output schema also removes the need to describe the return shape.

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 with the verb first and the returned fields enumerated after it. No filler, no repetition of the title, and nothing that could be cut.

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 zero parameters, an output schema, and a readOnly annotation, the definition covers what an agent needs in order to call it correctly. The only gap is the unstated authentication precondition, which is a real but minor omission for a personal-account lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly makes no attempt to explain inputs, since none exist.

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 enumerates exactly what is retrieved: euro credit balance, loyalty points overview, tier status, and active article missions. That is clearly distinct from siblings like rewe_get_coupons or rewe_get_discounts, though the description never explicitly contrasts itself with rewe_get_profile, which could also carry loyalty data.

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 this is the tool for checking one's loyalty/bonus standing, but there is no explicit when-to-use statement, no mention of the alternative sibling tools, and no prerequisite such as needing to be authenticated (a sibling rewe_auth_status exists).

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