Gaurmon

Price history for an item

price_history

Read-onlyIdempotent

An item's observed unit-price range (min, median, max per kg, L or item) by flyer week (Thursday to Wednesday), from flyer offers and shelf prices near a place, plus longRun: the Statistics Canada monthly average unit price for the item since 2017 (Ontario, else Canada), with its 1- and 5-year change. weeksKnown says how many weeks Gaurmon has: its history started with the Oct 29 2026 flyer week and grows by one each Thursday, so say so when it's short, and say longRun is a provincial average, not a store price.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item": "<item>"
    },
    "name": "price_history"
  }
}

Input Schema

Name	Required	Description
`item`	Yes	The generic item, as compare_items takes it: "chicken thighs", "large eggs", "bananas". Not a brand or receipt code.
`near`	No	Where the shopper is: a Canadian postal code ("M6H 2B6"), an FSA ("M6H"), or "lat,lng".
`unit`	No	Compare in this unit (default: the one most prices use).
`weeks`	No	How many flyer weeks back, including this one (default 8).
`radiusKm`	No	Search radius in km around `near` (default 5).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4/5.0

Behavior5/5

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

Although annotations already declare this as a safe read-only, idempotent operation, the description adds substantial context: data sources, Thursday-to-Wednesday flyer weeks, the Oct 29 2026 history start, how weeksKnown grows, and the provincial-average limitation of longRun.

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 purpose is front-loaded in the first sentence, and the second sentence focuses on important output caveats. It is dense but not padded, though the single-paragraph forcefulness makes it slightly harder to scan.

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 five-parameter tool with no output schema, the description supplies enough detail about returned fields (range, longRun, 1- and 5-year change, weeksKnown) and their limitations for an agent to use it correctly.

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 description coverage is 100%, so all five parameters are already documented in the schema. The description reinforces concepts like unit prices and flyer weeks but adds little parameter-level meaning beyond what is already structured.

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

Purpose4/5

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

The description clearly identifies a specific retrieval tool: an item's observed unit-price range by flyer week, plus Statistics Canada long-run averages. It does not explicitly distinguish itself from the sibling price_range tool, so it falls short of the highest clarity mark.

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

Usage Guidelines3/5

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

Usage is implied through terms like 'observed unit-price range' and 'flyer week', but the description never states when to choose this over price_range or compare_items. It offers caveats about interpreting weeksKnown and longRun, but not selection guidance.

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

All Gaurmon 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?