Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Search REWE Supermarkets

rewe_search_markets
Read-only

Search REWE stationary supermarkets by city, street, market name, or German postal code to find nearby store locations and plan a grocery trip.

Instructions

Search REWE stationary supermarkets by city, street, market name, or German postal code (PLZ).

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": {
      "query": "<query>"
    },
    "name": "rewe_search_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCity, street, market name, or zip code (e.g. 'Köln', '50667', 'Berlin Alexanderplatz').

Output Schema

NameRequiredDescriptionDefault
countYes
marketsYes

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 is consistent with a search operation. Beyond the annotation, the description adds only the qualifier "stationary" (physical stores, not delivery) — useful disambiguation — but says nothing about result limits, pagination, multi-match behavior, or empty-result handling.

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 that names the action, the resource, and every accepted key type. Nothing is wasted and nothing important is buried.

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 one required parameter, a read-only annotation, an output schema covering the return shape, and full schema coverage, the definition covers everything needed to call the tool correctly. Only search-behavior edge cases (multiple matches, no matches) are 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 coverage is 100% and the single query parameter is fully documented in the schema, including example values. The description restates those same key types without adding format or normalization rules, so baseline 3 applies.

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?

A specific verb+resource ("Search REWE stationary supermarkets") with the searchable fields named, so an agent can distinguish it from rewe_get_market_details or rewe_set_selected_market. It stops short of naming a sibling alternative explicitly, so it lands at 4 rather than 5.

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?

The listing of accepted lookup keys implies the discovery use case, but there is no explicit when-to-use or when-not-to-use guidance and no pointer to rewe_get_market_details for follow-up detail. Usage is inferable rather than stated.

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