Skip to main content
Glama

VynnAI Canadian grocery prices

Search the grocery catalogue

search_products
Read-only

Search Canadian grocery products by name or brand in one province. Use this when you have a description rather than a barcode. Province is required because the search service does not publish a national mixed-store result. Returns catalogue entries with current prices, not a price history. The result includes open_in_vynn_url, an absolute Vynn web link that carries the query. The linked page sets its own store scope, so its prices may differ from this result.

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": {
      "query": "<query>",
      "province": "<province>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (1-100, default 20).
queryYesSearch text, matched against product name and brand.
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
Behavior3/5

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

Annotations already declare readOnlyHint/destructiveHint=false, so the safety profile is covered; the description adds genuinely non-structured context: results carry current prices only, each entry contains an absolute web link carrying the query, and that linked page applies its own store scope so prices may diverge. Those caveats are valuable and not derivable from annotations. It stops short of noting no pagination behavior or result ordering, keeping it at a solid 3 with annotations doing part of the work.

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?

Front-loaded with the action and scope, then usage routing, then return-value caveats — a logical order with no filler. It runs five sentences, and the final two about open_in_vynn_url, while useful, could be compressed, so it is efficient rather than maximally tight.

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?

No output schema exists, and the description compensates by describing what comes back (catalogue entries with current prices, plus an absolute open_in_vynn_url) and warning about price divergence on the linked page. Combined with 100% parameter coverage and read-only annotations, an agent has everything needed to call and interpret it.

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 goes modestly beyond by explaining the rationale for the required province (no national mixed-store results) and by flagging that entries return an open_in_vynn_url field. It does not add matching behavior or syntax detail for query beyond what the schema already documents.

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?

States a specific verb and resource ('Search Canadian grocery products by name or brand in one province') and immediately distinguishes itself from lookup_product by saying to use it 'when you have a description rather than a barcode'. An agent can pick it apart from siblings without opening the schema.

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?

Explicitly names the selecting condition versus lookup_product (description vs. barcode) and versus price_history ('current prices, not a price history'). It also explains why province is mandatory (the service publishes no national mixed-store result), which is a usage constraint, not just a parameter fact.

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