Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Get Configured Default REWE Market

rewe_get_selected_market
Read-only

Retrieve the active default REWE market ID, postal code, and service type (pickup or delivery) to confirm the current shopping context before product searches or trip planning.

Instructions

Show the currently active default REWE marketId (wwIdent), zipCode (PLZ), and serviceType (PICKUP or DELIVERY).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
cityNo
zipCodeYes
marketIdYes
updatedAtNo
marketNameNo
serviceTypeYes

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?

The readOnlyHint annotation already establishes that this is a safe, side-effect-free read. The description adds the useful fact that it reports the currently *configured* state (not a lookup), but it does not say what happens when no market has been configured yet (error, null, or fallback), which is the main behavioral unknown for a getter of stored state.

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?

A single front-loaded sentence with no filler. The field names and enum values are packed inline and every clause carries information.

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?

For a zero-parameter read tool with a full output schema and a readOnly annotation, the description covers what it is and what state it reports. The only meaningful omission is the empty/unconfigured case, which matters because the sibling setter implies the value may not exist yet.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The mention of the concrete field identifiers is helpful framing but not parameter-related.

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 ('Show') plus a precisely scoped resource ('currently active default REWE market') and names the exact fields returned (marketId/wwIdent, zipCode/PLZ, serviceType). It implicitly contrasts with the mutating sibling rewe_set_selected_market through the word 'active default', but never names that or any other 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no alternative is named. An agent must infer that this is the read-side counterpart to rewe_set_selected_market and is distinct from rewe_search_markets or rewe_get_market_details; nothing in the text routes it.

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