Skip to main content
Glama

VynnAI Canadian grocery prices

Price history for one SKU

price_history
Read-only

Observed price series for a single retailer SKU over a lookback window. IMPORTANT: the identifier is a retailer-scoped SKU (an external_sku), not a UPC — passing a barcode here will not resolve. Use lookup_product or search_products first to obtain a SKU. A province is required, because the series is scoped to that province's reference stores. Prices are observed on our reference-store panel and are not guaranteed to match every store. When the product name is available, the result includes open_in_vynn_url, an absolute Vynn web link that searches for it; the linked page sets its own store scope, so its prices may differ from this series.

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": {
      "sku": "<sku>",
      "banner": "<banner>",
      "province": "<province>"
    },
    "name": "price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYesRetailer-scoped SKU, from a lookup or search result.
bannerYesRetailer banner slug that scopes the SKU, e.g. 'metro'.
periodNoLookback window in days, e.g. '30d' or '90d'. Default '90d'.90d
provinceYesTwo-letter Canadian province or territory code, e.g. 'ON', 'BC', 'QC'. Coverage is Canada only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint=false annotations, the description discloses that prices come from a reference-store panel and may not match every store, and that the returned open_in_vynn_url points at a page with its own store scope that can differ from this series. These caveats are non-obvious and materially affect how an agent should present results.

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 scope and the SKU-vs-UPC warning are front-loaded, and each subsequent sentence addresses a distinct pitfall (province requirement, panel sampling limits, open_in_vynn_url scope). It is slightly long, and the open_in_vynn_url sentence could be trimmed, but nothing is redundant with the schema.

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 read-only, four-parameter tool with no output schema, the description covers the identifier format, the required province rationale, the sampling caveat on returned prices, and the semantics of a returned URL field. Nothing an agent needs to call or interpret this 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 a baseline of 3 applies, but the description adds real meaning the schema only hints at: 'sku' is an external_sku (not a UPC) and 'province' is required because the series is scoped to that province's reference stores. Only 'period' and 'banner' are left entirely to the schema, which documents them adequately.

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 first sentence states a specific verb and resource — an observed price series for a single retailer-scoped SKU over a lookback window — and the mention of external_sku plus the pointer to lookup_product/search_products separates it cleanly from the siblings. An agent knows immediately what this returns and what it does not.

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

Usage Guidelines5/5

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

It gives explicit prerequisites ('Use lookup_product or search_products first to obtain a SKU'), an explicit exclusion ('passing a barcode here will not resolve'), and the condition for the required province ('because the series is scoped to that province's reference stores'). These are exactly the when/when-not/alternatives signals an agent needs.

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