Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Get REWE Product Details & Nutrition

rewe_get_product_details
Read-only

Fetch detailed REWE product information by product ID, including ingredients, allergens, nutrition, GTIN, and listing price.

Instructions

Fetch detailed product information including description, ingredients, allergens, nutrition table, GTIN, and listing price.

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": {
      "productId": "<productId>"
    },
    "name": "rewe_get_product_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipCodeNoGerman postal code (PLZ, e.g. '50667'). Defaults to the configured zip code.
marketIdNoREWE market identifier (wwIdent, e.g. '840174'). Defaults to the configured market.
productIdYesREWE productId from rewe_search_products.
serviceTypeNoREWE service type ('PICKUP' for Abholservice or 'DELIVERY' for Lieferservice).

Output Schema

NameRequiredDescriptionDefault
idYes
priceNo
titleYes
allergensNo
descriptionNo
ingredientsNo

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?

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context. It adds the returned data domains, which is mildly useful, but says nothing about how zipCode/marketId/serviceType affect availability or price, and nothing about failure behavior for invalid productIds.

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?

One front-loaded sentence, no filler, and the field enumeration is compact. It is slightly list-heavy but every item conveys scope that an agent would otherwise have to guess.

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?

With an output schema present, return shapes need not be explained, and the description covers the payload domains. However, for a context-sensitive lookup whose price depends on zipCode, marketId, and serviceType, the description omits that dependency, leaving a meaningful gap in how an agent should set the optional parameters.

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%, including the enum for serviceType and defaults for zipCode/marketId, so the schema already carries parameter meaning. The description adds no parameter-level detail beyond implying price is returned; baseline 3 applies.

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?

Specific verb ('Fetch') plus resource ('detailed product information') with an enumerated payload: description, ingredients, allergens, nutrition table, GTIN, listing price. It is clearly a detail-lookup as opposed to the search siblings, though it does not name rewe_search_products directly.

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?

The description gives no when-to-use guidance, no prerequisites, and no alternatives. The only routing hint ('productId from rewe_search_products') lives in the input schema, not the description, so an agent reading the description alone gets no help choosing between this and the search/list tools.

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