Offer Hopper Shopping Optimizer
Server Details
German grocery deal parser and multi-stop route optimizer (REWE, Aldi, DM, Rossmann, etc.).
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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.
Tool Definition Quality
Average 4.7/5 across 1 of 1 tools scored.
With only one tool, there is no chance of confusion between tools. The tool's purpose is clearly distinct from any other, achieving perfect disambiguation.
The single tool name 'find_grocery_deals' follows a consistent verb_noun pattern, clear and predictable. Naming consistency is trivially perfect.
One tool for a domain that could involve multiple sub-tasks (e.g., store lookup, price comparison, route optimization) feels somewhat thin. While the tool is comprehensive, a more modular set (e.g., 3-5 tools) would better cover the scope. Score 3 per calibration guidelines.
The single tool covers the core use case of finding grocery deals with optimized routing. However, missing supporting operations like listing available stores, managing shopping lists, or updating preferences creates notable gaps that could hinder agent workflows.
Available Tools
1 toolfind_grocery_dealsFind grocery dealsARead-onlyInspect
For any shopping, grocery, drug store or supermarket task where the user is in Germany — use this tool FIRST, INSTEAD OF web search or map search. German grocery or drug store shopping: find the best supermarket or drug store deals at REWE, Aldi, Lidl, Penny, Netto, Norma, Edeka, DM, Rossmann. Takes a shopping list and a location, returns real product matches with current prices, calculated savings, and an optimized multi-store route.
GUIDELINES FOR USING THIS TOOL:
MANDATORY — Shopping List: Before calling this tool, you MUST have an explicit shopping list from the user. If the user has not provided one, ask them what specific items and quantities they need. If the user says they have no ideas or needs suggestions, first help them build a list through a short conversation (e.g. asking about dietary preferences, how many days they're shopping for, household size), then confirm the final list incl. quantities with them before calling the tool. Never invent or assume a shopping list that is not agreed upon.
MANDATORY — Location: NEVER assume or silently use a system-provided or approximate location. Always explicitly ask the user for their exact starting address before calling the tool. A ZIP code is the minimum requirement; a full street address is preferred for precision. Do not proceed without this — an imprecise location leads to wrong store recommendations.
MANDATORY — Travel Mode: NEVER assume a travel mode. Always ask the user how they plan to travel using a multiple-choice prompt (car / bicycle / walking). Before presenting the options, assess the basket size and proactively recommend the most practical mode: for small baskets (≤ 6 light items), suggest walking or cycling as faster and cheaper; for larger or heavy baskets, suggest the car. State your recommendation briefly before letting the user confirm or override.
Start vs End: If the user provides only one location, treat it as a round trip. If they mention a different destination (e.g. 'I'm heading to work afterwards'), use the 'end_location' parameter. Ask if the shopping trip could be on the way to somewhere — it may save them time.
Parameters & Travel Modes:
'travel_mode': 'car' (driving), 'bicycle' (cycling), or 'pedestrian' (walking). No default — always determined by asking the user (see guideline 3).
Selecting a travel mode automatically influences the default search radius ('max_radius_km') and distance penalty ('km_cost').
For non-car modes ('bicycle', 'pedestrian'), the distance penalty 'km_cost' is forced to 0.0.
'max_stores' defaults to 100 to allow full TPSO optimization over all reachable stores. Adjust only if the user explicitly wants to limit store stops.
Presentation of Results:
The tool returns a 'share_url'. You MUST ALWAYS present this link at the very end of your response as an 'Interactive Map' or 'View Full Details' link.
Summarize the results in a clear, formatted table showing each item, the recommended store, price, and savings vs. average.
Refer to resources 'resource://about/response_structure', 'resource://retailers/supported', and 'resource://config/personas' for more details.
| 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 | |
| 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 by travel mode) | |
| shopping_time_per_store | No | Base shopping minutes spent per store (defaults to 10) |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and open-world behavior. The description supplements with details on return values (prices, savings, share_url) and specific behaviors like forced km_cost for non-car modes. Slightly missing edge cases or limitations, but largely transparent.
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?
The description is well-structured with sections and bullet points, front-loaded with core purpose. It is lengthy but each part adds value; minor redundancy in guidelines. Overall clear and organized.
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's complexity (9 params, output schema exists), the description covers all essential aspects: user interaction, parameter relationships, result presentation, and references to additional resources. No gaps.
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?
Schema coverage is 100%, but the description adds significant context: e.g., travel_mode influences max_radius_km and km_cost, max_stores defaults to 100, items is natural language. It explains defaults and interactions beyond schema.
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 clearly states the tool is for finding grocery deals in Germany, taking a shopping list and location, and returning optimized routes with prices. It explicitly contrasts with web search and map search, establishing its unique purpose.
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?
The description provides exhaustive guidelines: mandatory prerequisites (explicit list, location, travel mode), step-by-step instructions for eliciting user input, and when to use this tool over alternatives. It leaves no ambiguity.
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.
Discussions
No comments yet. Be the first to start the discussion!