Barcode Report

Look up several barcodes

lookup_barcodes

Read-onlyIdempotent

Find the products for up to 100 barcodes in one call. Duplicates are ignored. Uses one lookup per distinct code; if the batch would exceed the remaining allowance, nothing is looked up or charged.

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": {
      "barcodes": "<barcodes>"
    },
    "name": "lookup_barcodes"
  }
}

Input Schema

Name	Required	Description	Default
`barcodes`	Yes	Barcodes to look up.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered; the description adds genuinely new behavior: duplicate codes are collapsed, cost is one lookup per distinct code, and the batch is all-or-nothing when the remaining allowance is insufficient.

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?

Three short sentences with zero padding; the batch limit and the quota/atomicity caveat are front-loaded where an agent will see them before invoking.

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

Completeness3/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 never says what comes back — whether results are keyed/ordered by input barcode, or what happens for codes that are not found — which is the main missing piece for a batch lookup. Everything about invocation cost and limits is otherwise well covered.

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% (the array, its 1-100 bounds and 32-char item limit are all documented), yet the description still adds meaning the schema cannot express: duplicate entries are ignored and billing counts distinct codes only.

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 opens with a specific verb and resource ('Find the products') plus an explicit batch scope ('up to 100 barcodes in one call'), which cleanly separates it from the singular sibling lookup_barcode and from 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 Guidelines3/5

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

Batch usage is implied by 'up to 100 barcodes in one call', but there is no explicit guidance on when to prefer this over lookup_barcode (single code) or search_products (fuzzy/name lookup), and no stated exclusions.

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

All Barcode Report 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?