offerhopper.ai Grocery and Drug Store Shopping Assistant
Server Details
German grocery and drug store real time prices and offers including optimal route planing
- 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.3/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion between tools. The agent can only select this single tool.
With only one tool, naming consistency is inherently maintained. The tool name 'find_grocery_deals' clearly describes its function using a verb_noun pattern.
The server has only one tool, which is too few for the apparent complexity of a grocery shopping assistant covering multiple stores, routes, and shareable lists. A more modular approach with separate tools for search, pricing, routing, and list management would be more appropriate.
The single tool bundles many features, but this makes it a monolithic operation. The domain likely requires separate operations like fetching store lists, updating shopping lists, or comparing individual stores, which are missing. The tool's scope is narrow despite its lengthy description.
Available Tools
1 toolfind_grocery_dealsFind grocery dealsARead-onlyInspect
Finds the best current grocery and drug store products, their prices and deals across German supermarkets and drug stores (REWE, Aldi, Lidl, Penny, Netto, Norma, Edeka, DM, Rossmann, Mueller) for a given shopping list and starting location in Germany. Returns real product matches with live prices, calculated savings vs. average single-store price, an optimized route, and a shareable interactive grocery list for easier shopping. 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 | |
| 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?
Beyond annotations (readOnlyHint, openWorldHint), the description adds valuable behavioral details: it returns live prices, calculated savings, an optimized route, and a shareable list. It specifies supported travel modes (car, bicycle, pedestrian) and explains how the tool behaves for corridor vs. round trips. No contradictions with annotations.
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 a concise paragraph of three sentences, front-loaded with the main purpose and scope. It covers key aspects without fluff. A slightly more structured format (e.g., bullet points) could improve scannability, but current form is efficient and easy to parse.
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 parameters, multiple outputs including route and shareable list) and the existence of an output schema, the description adequately summarizes the main use case and output types. It lists the supported stores and travel modes. Minor omissions like max_stores or shopping_time_per_store are covered by the schema, so completeness is high.
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?
The input schema has 100% description coverage, so the baseline is 3. The description references some parameters (items, location, end_location, travel_mode) but does not add significant meaning beyond the schema's own parameter descriptions, which are already detailed (e.g., km_cost forced to 0.0 for bicycle/pedestrian). Thus, the description adds minimal extra value for parameter semantics.
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's purpose: finding best grocery deals across specific German stores for a given shopping list and location. It specifies the verb (find), resource (grocery deals), scope (German supermarkets), and outputs (products, prices, savings, route). With no siblings, differentiation is not needed.
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 usage context: for corridor trips (A-to-B) the 'end_location' parameter should be supplied. It also implies use when comparing prices across stores. However, no explicit alternatives are mentioned since there are no sibling tools, so the score reflects clear but non-comparative guidance.
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!