Skip to main content
Glama

Prices of one product by barcode

product_prices
Read-onlyIdempotent

Gives one product's price at each Israeli supermarket chain's online store, by its barcode: the price per chain, the cheapest chain, the gap between cheapest and dearest, the date of the prices and the product's page on Ramzii. Example barcode: "7290000066318".

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": {
      "barcode": "<barcode>"
    },
    "name": "product_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
barcodeYesThe product's barcode (6 to 14 digits), e.g. "7290000066318".

Output Schema

NameRequiredDescriptionDefault
open_urlYesA www.ramzii.co.il link that opens this answer.
data_dateYesIsraeli day (YYYY-MM-DD) of the oldest price in the answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world lookup, so the safety profile is well covered. The description adds meaningful scope context — coverage is limited to Israeli supermarket chains' online stores — and enumerates the content returned per chain; it says nothing about rate limits or failure behavior, but the annotation bar is low here.

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?

Everything is packed into one front-loaded sentence whose first clause names the resource and key, followed by an output enumeration and a sample value. The long comma-separated list of returned fields is dense but each item is informative; no filler sentences.

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?

For a single-parameter lookup with an output schema and strong annotations, the description supplies enough context to call it correctly — scope, key format, and an example. The only omission is what occurs when a barcode is not found in any chain, which is minor given the output schema's presence.

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?

With a single parameter at 100% schema description coverage including a pattern and example, the schema already carries the semantics completely. The description repeats the barcode key and gives the same style of example, adding no additional meaning beyond the schema.

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 states a concrete verb and resource: it returns one product's price at each Israeli supermarket chain's online store, keyed by barcode. The 'one product' scope implicitly separates it from basket comparison and product search siblings, though no sibling is named outright.

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 only implied: the barcode is presented as the lookup key with a concrete example, so an agent can infer this is the per-product lookup path. There is no explicit statement of when to prefer it over compare_basket or search_products, and no note about what happens for unknown barcodes.

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