Cheapest Grocery Basket

Price a whole shopping list at each store

price_basket

Price an entire shopping list at every collected store in a ZIP, one complete basket per store. Returns per-store line items with quantities and line totals, the basket subtotal, exactly which requested items that store is missing, whether the basket is complete, stock flags, and the oldest price in the basket so staleness is visible. Use this when the shopper will make one trip and wants to know where the whole list is cheapest. Accepts quantities as 'milk x2'. Costs $0.01 USDC per call via x402 on Base.

Input Schema

TableJSON Schema

Name	Required	Description
`zip`	Yes	5-digit US ZIP code, e.g. '30501'.
`mode`	No	Optional fulfillment intent: 'pickup' or 'delivery'. Recorded on the response; delivery fees and minimums are not collected yet and are returned as null rather than estimated.
`items`	Yes	Comma-separated shopping list, optionally with quantities, e.g. 'milk x2, eggs, bread, butter'. A JSON array of {name, quantity} is also accepted.
`stores`	No	Optional comma-separated chains to restrict to, e.g. 'aldi,publix'.
`maxAgeDays`	No	Optional freshness limit in days (default 14, max 120). A price read longer ago than this is withheld rather than returned as if current; raise it to accept older readings.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 4, 2026
- addedInput schema / properties / items / examples
```
Added value: +[
+  "milk x2, eggs, bread, butter"
+]
```
- addedInput schema / properties / maxAgeDays / examples
```
Added value: +[
+  14
+]
```
- addedInput schema / properties / mode / examples
```
Added value: +[
+  "pickup"
+]
```
- addedInput schema / properties / stores / examples
```
Added value: +[
+  "aldi,publix"
+]
```
- addedInput schema / properties / zip / examples
```
Added value: +[
+  "30501"
+]
```

Changed1 schema field changedAug 24, 2026

addedInput schema / properties / maxAgeDays

Added value: +{
+  "description": "Optional freshness limit in days (default 14, max 120). A price read longer ago than this is withheld rather than returned as if current; raise it to accept older readings.",
+  "maximum": 120,
+  "minimum": 1,
+  "type": "integer"
+}

First observedAug 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly: it discloses the $0.01 USDC x402 payment cost, staleness visibility via oldest-price reporting, missing-item behavior, and the limitation that delivery fees and minimums are returned as null rather than estimated.

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?

The description is dense but every sentence earns its place: function, return contents, use case, and cost/payment. It is front-loaded with the core behavior and contains no fluff or tautology.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema and no annotations, the description is unusually complete: it explains the return fields, the trip-planning use case, the pricing model, missing-item handling, staleness, and mode limitation. Nothing essential is left unexplained.

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%, so the schema already documents all five parameters. The description adds little beyond the schema, only restating the 'milk x2' quantity convention already present in the items examples. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Price an entire shopping list at every collected store in a ZIP, one complete basket per store.' It clearly differentiates from siblings like cheapest_basket by emphasizing per-store line-item baskets, missing-item reporting, and completeness flags.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit context: 'Use this when the shopper will make one trip and wants to know where the whole list is cheapest.' It does not name alternative tools or state when not to use it, so it stops short of a perfect 5.

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

All Cheapest Grocery Basket tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?