Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Add or Remove Product in REWE Favorites List

rewe_manage_favorite
Idempotent

Add a product to a REWE favorites list or remove an entry from one using list and item IDs. Manage saved grocery items and keep favorites current.

Instructions

Add a product (listingId, optional productId) to a REWE favorites list or remove an entry (itemId) from a favorites list.

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": {
      "action": "<action>",
      "listId": "<listId>"
    },
    "name": "rewe_manage_favorite"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesWhether to 'add' or 'remove' an item.
itemIdNoRequired when action='remove': line item ID (`itemId`) from rewe_get_favorites.
listIdYesFavorites list ID from rewe_get_favorites.
quantityNoOptional preferred quantity when action='add'.
listingIdNoRequired when action='add': product listingId.
productIdNoOptional productId when action='add'.

Output Schema

NameRequiredDescriptionDefault
actionYes
listIdYes
resultYes

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=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the action-specific requirement structure but says nothing about authentication needs, duplicate-add behavior, or what happens to the list entry on removal, which would be valuable context for a mutation tool.

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 front-loaded sentence with the mutation scope stated first and per-action parameters grouped in parentheses. It is efficient, though the nested parentheticals are slightly dense to parse.

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 described, and annotations carry the safety profile. The description covers both operating modes adequately; only edge-case behavior (duplicate add, nonexistent item) is left unaddressed.

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%, so the schema already documents each parameter, including the conditional requirements. The description restates the add/remove parameter mapping but adds no syntax, format, or sourcing detail beyond what the schema provides.

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 names a specific verb pair (add/remove) and resource (REWE favorites list), and the parenthetical parameter hints make the two modes unambiguous. It does not explicitly name or differentiate itself from siblings such as rewe_get_favorites, though the schema references it.

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?

Usage is implied rather than stated: the agent must infer that this tool is the write counterpart to rewe_get_favorites, and that listId/itemId come from a prior favorites lookup. No explicit when-to-use or when-not-to-use guidance is provided, though the add/remove split is clear from the description and schema.

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