Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Get REWE Bonus & App Coupons

rewe_get_coupons
Read-only

Fetches available and activated REWE Bonus and personal digital app coupons so users can review current discounts and savings.

Instructions

Fetch available and activated REWE Bonus and personal digital app coupons.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countYes
couponsYes

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 that this is a safe read, so the description's burden is lower. It adds a useful behavioral detail by disclosing that both available and activated coupons are returned, but says nothing about auth requirements, personalization scope, or whether results are market-dependent — all plausible for a coupon endpoint.

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 no filler. The resource and the two coupon categories are stated immediately, leaving nothing superfluous to parse.

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?

For a parameterless read tool with an output schema and readOnly annotations, the description covers what is needed to call it correctly. Return-value structure is documented by the output schema, so the description need not restate it.

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 the baseline is 4 and there is no parameter meaning for the description to add or omit. The schema imposes nothing the agent needs explained.

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 (fetch) and a specific resource (REWE Bonus and personal digital app coupons), and it clarifies the two coupon states covered (available and activated). It stops short of differentiating itself from nearby siblings such as rewe_get_bonus, rewe_get_discounts, or rewe_search_discounts, so an agent must still infer which of these overlapping offers-tools to call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of prerequisites such as authentication, and no pointer to an alternative tool. The only implicit signal is that the tool returns both available and activated coupons in one call, but nothing tells the agent when to prefer this over the bonus or discounts siblings.

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