Skip to main content
Glama

Yappman Data Supermarket Price Snapshots

Christmas dinner basket, weekly summary

get_christmas_basket_prices
Read-onlyIdempotent

Returns one week of the UK Christmas dinner basket summary (weekly to 24 Dec 2026): posted shelf prices of numbered items at Tesco, Sainsbury's, Asda and Aldi with flags, or totals over the items each retailer priced. Item numbers only, no product names. Not a CPI and not a price comparison: retailers in a fixed order, never by price; totals cover different items. Weekly snapshots, not live; the open week changes until Sunday. Omit week for the latest. Quote the notes with any total.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_christmas_basket_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNo"totals" (each retailer total over the items it priced, and the count) or "items" (the price and flags of each item). Omit for "totals".
weekNoISO week, e.g. "2026-W45". Omit for the latest week held.
retailerNoOnly this retailer, e.g. "asda". Omit for all four.

Output Schema

NameRequiredDescriptionDefault
asOfYes
viewYes
weekYes
itemsNo
notesYes
titleYes
weeksYes
creditYes
notCpiYes
byRetailerNo
weekClosedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description still adds substantial context beyond them: the data is weekly snapshots rather than live, the open week keeps changing until Sunday, items are numbered with no product names, and the notes must be quoted alongside any total. These are exactly the caveats an agent needs to avoid presenting stale or misleading figures.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core capability is front-loaded in the first clause and every subsequent sentence adds a distinct caveat rather than repeating the schema. It is telegraphic and clause-dense, which makes it slightly harder to parse, but there is no filler or restatement of structured fields.

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?

With an output schema present, return values need not be explained, and the description instead spends its space on the interpretation hazards (non-comparability of totals, fixed retailer order, non-live snapshots, mandatory notes). For a small, fully-annotated read tool, nothing an agent needs in order to call it or report it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not carry: 'Omit week for the latest' is reinforced by the volatile-open-week behavior, and 'Item numbers only, no product names' frames what the items view actually yields. The retailer and view parameters are left entirely to the schema, which is acceptable given full enum documentation.

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 states a specific verb and resource ('Returns one week of the UK Christmas dinner basket summary'), names the retailers, and specifies the two shapes of output (per-item prices with flags, or per-retailer totals). It actively distinguishes itself from adjacent concepts by declaring what it is not ('Not a CPI and not a price comparison'), so an agent can tell it apart from the index-style sibling without opening a schema.

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?

Usage is well signposted: 'Omit week for the latest', 'retailers in a fixed order, never by price', and 'totals cover different items' tell the agent exactly how to call and how not to read the result. The gap is sibling routing — it disqualifies comparison/CPI use cases but never names which tool to use instead, leaving that inference to the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources