Live prices, deals & optimal multi-stop shopping routes for German grocery & drug stores.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 5/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusing it with another. The tool's purpose is clearly and uniquely defined.
With a single tool, there is no pattern to be inconsistent with. The name follows a descriptive verb_noun style and accurately reflects the tool's function.
The server purports to be a full shopping assistant for German supermarkets and drugstores, yet it exposes only one monolith tool. This is too few for the apparent scope, as agents would benefit from separate operations for browsing offers, managing lists, or handling different query types.
The single tool covers route planning, product matching, savings calculation, and travel modes, but it explicitly excludes common assistant tasks like 'what's on offer near me' and provides no granular operations for managing shopping lists or offers. The core workflow is present, but the surface feels thin for the stated domain.
plan_optimal_shopping_routePlan optimal grocery and drug store shopping tripAPlans the optimal shopping trip for a given list and starting location in Germany. Answers 'where should I go to buy this list, and is the trip worth it?' — not 'what's on offer near me'. Matches each item on the list to the best current offer across German supermarkets and drug stores (REWE, Aldi, Lidl, Penny, Netto, Norma, Edeka, DM, Rossmann, Mueller), then computes the cheapest realistic route by weighing product prices against travel distance and shopping time. Returns the chosen store(s), the per-item picks with live prices, the trip's savings and a worth-it verdict, and a shareable interactive grocery list. Supports car, bicycle, and pedestrian travel modes. For corridor trips (A-to-B), supply 'end_location' to route stores along the way.
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | The shopping list in natural language (e.g. '3x milk, eggs, bread') | |
| km_cost | No | Travel cost penalty per kilometer (forced to 0.0 for bicycle/pedestrian) | |
| location | Yes | Starting location (ZIP code, city, or address in Germany) | |
| hour_cost | No | Time cost penalty in EUR per hour (defaults to 12.0) | |
| max_stores | No | Maximum number of store stops to allow in the route (default: 100) | |
| travel_mode | No | Travel mode to use | car |
| end_location | No | Optional destination location if not a round trip | |
| max_radius_km | No | Maximum search radius in kilometers (defaults: car=15km, bicycle=5km, pedestrian=2km) | |
| shopping_time_per_store | No | Base shopping minutes spent per store (defaults to 10) |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already mark the tool as readOnly, idempotent, and non-destructive. The description adds significant behavioral detail on top: it matches items to current offers across named German retailers, weighs prices against travel distance and shopping time, returns a route, per-origin picks with live prices, a worth-it verdict, and a shareable list, and supports multiple travel modes.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Every sentence in the delivery earns its place: it states the core task, disambiguates it, explains matching and routing logic, lists what is returned, and adds a useful corridor-trip extension. The phrasing is front-loaded with the primary purpose and remains dense without fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 9 parameters and a rich output schema, the description still covers the essential completeness: what inputs are expected, how the optimization behaves, which stores/modes are supported, what the output contains, and when `end_location` matters. No critical operational gap remains.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Although the schema already covers all 9 parameters, the description adds important semantics beyond field titles: it explains that `km_cost` and `hour_cost` affect the travel-time/price trade-off, that `end_location` shifts routing from a round trip to a corridor trip, and that `travel_mode` includes the relevant urban modes. This helps an agent select and set parameters meaningfully.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource combination: 'Plans the optimal shopping trip for a given list and starting location in Germany.' It further clarifies its purpose by contrasting the answer it provides ('where should I go to buy this list...') with what it does not do ('not what's on offer near me').
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It clearly states when the tool is applicable: given a shopping list and starting location, it determines which stores to visit and whether the trip is worth it. It also gives an explicit usage variant for corridor trips via `end_location`, making the applicable contexts concrete even though no sibling tools are listed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!