Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Analyze Regular REWE Products from Purchase History

rewe_regular_products
Read-only

Analyze past online grocery orders to find frequently bought products, average prices, purchase frequency, and items due for restock.

Instructions

Analyze previously purchased products and online order history to identify frequently bought groceries, average prices, purchase cadence, and items due for restock.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
maxOrdersNoMaximum number of recent online orders to inspect (default: 15).
minPurchasesNoMinimum purchase count threshold (default: 1).

Output Schema

NameRequiredDescriptionDefault
noteNo
ebonsCountYes
minPurchasesYes
ordersAnalyzedYes
ordersAvailableYes
regularProductsYes
totalUniqueItemsYes
purchasedProductsCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation, so the description carries a lighter burden. It adds useful scope by saying the analysis draws on online order history and returns derived metrics, but it does not disclose limitations, data freshness, or how the order-inspection limit affects results.

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?

The definition is a single front-loaded sentence that states the analysis target and lists the key derived outputs without any filler. Every phrase contributes to understanding what the tool produces.

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?

The output schema exists, so the description need not explain return values, and the readOnly annotation covers safety. However, for a tool with three optional parameters and several related siblings, the definition leaves gaps around parameter interpretation and when to choose this over order-listing or search tools.

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

Parameters2/5

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

Schema coverage is only 67%, and the description adds no parameter-specific meaning at all. The limit parameter is undocumented in the schema and unexplained in the description, and the description does not clarify how maxOrders or minPurchases shape the analysis.

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, 'Analyze,' and clearly scopes the resource to previously purchased products and online order history. It also names the concrete outputs: frequently bought groceries, average prices, purchase cadence, and restock items. It does not explicitly distinguish itself from related siblings such as rewe_list_orders, which keeps it from 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 Guidelines3/5

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

The description implies the tool should be used when an agent needs purchase-history insights rather than raw order listing, but it never explicitly states when to use this versus alternatives. There are no exclusions, prerequisites, or named sibling alternatives to guide selection.

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