Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Get REWE Favorite Product Lists

rewe_get_favorites
Read-only

Fetch saved REWE favorite lists with product details, listingIds, and prices for your configured market; optionally include full product metadata.

Instructions

Fetch your saved REWE favorite lists along with product details, listingIds, and prices for the configured 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_favorites"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeProductsNoInclude full product metadata and listingIds (default: true).

Output Schema

NameRequiredDescriptionDefault
countYes
listsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context beyond that – results are scoped to the configured market and include listingIds and prices – but says nothing about authentication state (a rewe_auth_status sibling exists) or what happens when no favorites exist.

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 with no filler; the resource leads and the returned fields follow. Slightly dense packing of three returned artifacts into one clause, but nothing is wasted.

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 an output schema present, return values need not be explained, and the description correctly limits itself to resource, scope, and content. Only the precondition around the configured market and authentication is left implicit, a minor gap for a single-parameter read tool.

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% for the single includeProducts parameter, so the schema already explains it. The description's mention of product details and listingIds implicitly reflects the default true behavior but never addresses the false/slim mode, adding little beyond the schema.

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 and resource ('Fetch your saved REWE favorite lists') and enumerates what comes back (product details, listingIds, prices). It is distinguishable from rewe_manage_favorite by the read verb, though it never names any sibling explicitly.

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?

Implies usage through the phrase 'for the configured market', which signals a selected market must already exist, but gives no explicit when-to-use guidance and does not point to alternatives such as rewe_manage_favorite for editing lists.

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