VynnAI Canadian grocery prices

The store panel behind the data

list_reference_stores

Read-only

The configured reference stores, one per banner and province, with their banner, province, coordinates and observations_30d: the store's price-event count over the trailing 30 days. A configured store can stop collecting; a store at 0 recorded no price events in that window. Call this to answer 'what does Vynn actually cover?' — it is the panel definition, not a directory of every grocery store in Canada. The result includes open_in_vynn_url, an absolute link to Vynn's retailer list on the web.

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": "list_reference_stores"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum results (1-500, default 200).
`banner`	No	Banner slug, e.g. 'metro', 'nofrills'.
`province`	No	Two-letter Canadian province or territory code, e.g. 'ON', 'BC', 'QC'. Coverage is Canada only.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, non-destructive, closed-world operation, but the description adds useful semantics beyond them: observations_30d is a trailing 30-day price-event count, zero means no recorded events, and a configured store can stop collecting. It also discloses that open_in_vynn_url is an absolute retailer-list link, though it does not describe ordering or pagination behavior.

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 compact and front-loaded: it states what is returned, defines observations_30d, warns about the zero case, clarifies the scope, and explains the URL field in three efficient sentences.

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 list tool with fully described parameters and no output schema, the description supplies the key return semantics, the coverage caveat, and the meaning of the most important field. An agent has enough context to call it correctly without opening more documentation.

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 the schema already explains limit, banner, and province, including the province enum and Canada-only scope. The description reinforces the banner/province granularity but adds no parameter-level syntax or constraints beyond 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?

The description names the exact resource: configured reference stores, one per banner and province, and lists the returned fields. It also explicitly distinguishes this panel definition from a directory of every grocery store in Canada, so an agent can separate it from product-oriented siblings like lookup_product and search_products.

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?

It gives a clear use case: call this to answer 'what does Vynn actually cover?' and explicitly excludes using it as a general store directory. It does not name a sibling alternative for other store-related questions, which keeps it below a 5.

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

All VynnAI Canadian grocery prices 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?