Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Get REWE Weekly Brochure / Prospekt Metadata

rewe_get_brochure
Read-only

Fetches digital brochure metadata for a REWE market so you can browse weekly offers and plan a grocery trip.

Instructions

Fetch digital stationary handout/brochure (Prospekt) metadata for a REWE market.

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

Input Schema

NameRequiredDescriptionDefault
marketIdNoREWE market identifier (wwIdent, e.g. '840174'). Defaults to the configured market.

Output Schema

NameRequiredDescriptionDefault
handoutYes
marketIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 safe read. The description adds a modest amount of context beyond that by clarifying the payload is "metadata" rather than the brochure itself, which matters because a sibling (rewe_get_ebon_pdf) deals in documents. It says nothing about per-market variability, freshness/cadence of weekly brochures, or what happens if no brochure exists for the market.

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 tight sentence with no filler, front-loading the verb and the resource. It is arguably over-compressed: the same word count could have carried a use-case clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the operation is a trivial read with one optional parameter. Still, for a market-scoped brochure fetch an agent would benefit from knowing the default-market behavior and whether an empty result is normal, neither of which is stated.

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%, and the single marketId parameter is documented as a wwIdent defaulting to the configured market, so the schema carries the semantics. The description adds nothing about how the market affects which brochure is returned, which is acceptable at this coverage level.

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 uses a specific verb ("Fetch") and a specific resource ("digital stationary handout/brochure (Prospekt) metadata for a REWE market"), so an agent can tell it returns brochure metadata rather than brochure content. It does not contrast itself with nearby siblings such as rewe_get_ebon_pdf or rewe_get_market_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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g. that a market must be selected), and no pointer to an alternative tool. The agent must infer the use case from the name alone.

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