Skip to main content
Glama

VynnAI Canadian grocery prices

Look up a product by barcode

lookup_product
Read-only

Resolve a UPC/EAN/GTIN barcode to the product it identifies and the current offers for it across Canadian grocery banners in one province. Requires a province because grocery prices are store-scoped: there is no single national price for a product. Returns an empty offer list, not an error, when the barcode is known but not currently carried. The result includes open_in_vynn_url, an absolute Vynn web link for this product.

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": {
      "upc": "<upc>",
      "province": "<province>"
    },
    "name": "lookup_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
upcYesThe barcode to resolve. UPC-12, EAN-13 and GTIN-14 all work.
limitNoMaximum offers to return (1-500, default 100).
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.4/5.0
Behavior4/5

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

Goes beyond the readOnly/openWorld annotations by disclosing that a known-but-unstocked barcode yields an empty offer list rather than an error, and that coverage is Canada only. Does not mention rate limits or offer ordering, but the key edge case is covered.

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?

Four sentences, each carrying distinct information: what, why the province, edge-case return behavior, and one notable output field. Front-loaded with the action before the caveats.

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

Completeness4/5

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

With no output schema, the description covers the shape of the result at a high level (offers list, product identity, open_in_vynn_url) and the empty-list case. An agent still doesn't know the full offer object fields, but enough is given to call and interpret the tool correctly.

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; the description adds genuine meaning by explaining the domain rationale for the province parameter (store-scoped pricing) rather than just restating it. The limit parameter is left entirely to the schema.

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?

Specific verb + resource: 'Resolve a UPC/EAN/GTIN barcode to the product it identifies and the current offers for it.' Scope (Canadian grocery banners, one province) is stated, which separates it from the free-text search_products sibling.

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?

Explains why a province is required (prices are store-scoped, no national price) and implicitly positions this as the exact-identifier path versus search_products. It stops short of explicitly naming the alternative or when to prefer it over search_products.

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