Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Get REWE Market Details

rewe_get_market_details
Read-only

Fetch full details for a REWE market by ID or the configured market, including opening hours, phone number, address, and in-store services.

Instructions

Fetch full details for a REWE market (wwIdent): opening hours, phone number, address, and in-store services.

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

Input Schema

NameRequiredDescriptionDefault
marketIdNoREWE market identifier (wwIdent, e.g. '840174'). Defaults to the configured market.

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
phoneNo
wwIdentYes
servicesNo
addressLineNo
openingHoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's main added value is naming the fields returned. It says nothing about error behavior for an unknown marketId or whether the default market must be configured first, which would be genuinely useful context beyond the annotation.

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?

One front-loaded sentence with the verb, resource, identifier, and returned fields; no filler or redundancy.

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, the description needn't explain return values, and one optional parameter plus a read-only annotation keeps the surface small. Only the fallback-to-configured-market behavior and failure modes are left implicit.

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 coverage is 100% and the single parameter is optional with a documented default, so the schema already carries the semantics. The description's mention of `wwIdent` merely restates the schema's identifier description rather than adding format or constraint detail.

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 ('Fetch full details') and resource ('REWE market'), and enumerates the returned content (opening hours, phone, address, services). It does not explicitly distinguish itself from siblings like rewe_get_selected_market or rewe_search_markets, though the 'defaults to the configured market' note hints at the relationship.

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 only implied: an agent can infer this is the tool for looking up a single market's details, but there is no explicit when-to-use guidance, no mention of when to prefer rewe_get_selected_market or rewe_search_markets, and no stated prerequisites.

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