Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Get REWE Member Profile

rewe_get_profile
Read-only

Retrieves authenticated REWE SSO user info, customer profile, REWE ID, and configured store settings to support personalized account and store-aware actions.

Instructions

Fetch authenticated REWE SSO userinfo, customer profile, REWE ID, and configured store settings.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
subNo
emailNo
reweIdNo
zipCodeNo
fullNameNo
lastNameNo
marketIdNo
firstNameNo
customerIdNo
serviceTypeNo
emailVerifiedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

The annotations provide the essential read-only behavior. The description reinforces this by using 'Fetch' and specifying the returned data, but adds no information regarding rate limits, latency, or error handling beyond the basic read-only nature.

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 description is extremely concise, delivering maximum informational value in a single, direct sentence without any redundant phrasing.

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

Completeness5/5

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

Given the tool has no parameters and a provided output schema, listing the categories of data retrieved (ID, settings, userinfo) makes the definition complete for an agent needing to invoke it correctly for profile data.

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

Parameters4/5

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

Since the schema contains zero parameters, the description is crucial for context. It clarifies that the fetch operation relies on 'authenticated REWE SSO userinfo,' which explains the implicit parameter requirement.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly lists the resource types and data retrieved (SSO userinfo, REWE ID, store settings), providing maximum clarity on what the tool provides.

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?

While it mentions 'authenticated,' it offers no guidance on when to use this tool versus other `rewe_get_` family tools (e.g., ordering history vs. profile information). It lacks explicit exclusion criteria.

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