Skip to main content
Glama

ShortSpec barcode facts

Product facts by barcode

barcode_facts
Read-onlyIdempotent

Returns the sourced facts we hold for one product barcode (GTIN-8/12/13/14): product name, brand, short statements each with its source link, licence and check date, recall records naming the code, and our page for the product. Use it to look up or cite what a product is. Do not use it for prices, stock, reviews or sellers; it has none. Most barcodes return state no_facts, which is not a safety statement.

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

Input Schema

NameRequiredDescriptionDefault
barcodeYesThe product barcode as digits only: 8, 12, 13 or 14 digits with a valid check digit.

Output Schema

NameRequiredDescriptionDefault
gtinYes
stateNo
api_versionYes

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?

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description goes further by warning that most barcodes return state no_facts and that this is not a safety statement — a genuinely non-obvious interpretation cue — plus notes that each statement carries its source link, licence and check date. It stops short of explaining pagination or result-size limits, which keeps it from a 5.

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 purpose, then usage boundary, then the no_facts caveat — a sensible ordering with no filler sentences. The middle enumeration is dense and reads as a packed list, which slightly taxes scanning but every item is informative.

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 single-parameter lookup with an output schema, the definition covers purpose, the exclusion set, and the dominant empty-result mode an agent will actually encounter. Nothing needed to call it correctly or to interpret the common failure case is missing.

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 coverage is 100% and the single parameter already documents the digit-only format, length set and check-digit requirement. The description's mention of GTIN-8/12/13/14 restates what the schema's pattern and parameter description already say, so it adds little beyond the structured field.

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 ('Returns the sourced facts we hold for one product barcode') and enumerates the payload: name, brand, sourced statements, licence, check date, recalls, product page. It also fixes the accepted identifier family (GTIN-8/12/13/14), so an agent knows exactly what it retrieves.

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?

Explicit when-to-use ('look up or cite what a product is') paired with explicit when-not ('prices, stock, reviews or sellers; it has none'). That negative scoping is the decisive routing signal and leaves little to inference.

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