Skip to main content
Glama

Packaged food by barcode or by name: product name, brand

food
Read-only

Packaged food by barcode (EAN-8, UPC-A, EAN-13 or GTIN-14) or by name: product name, brand, quantity, Nutri-Score, NOVA group, nutrients per 100 g (energy, fat, saturated fat, carbohydrates, sugars, fibre, protein, salt), allergens, labels, ingredients text and front image URL. Open Food Facts data (ODbL, attribution in source). A barcode not in the database is a 404, not charged. Community data: values can be missing or wrong. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
nameNoProduct name words, 2 to 100 characters (optional, when no barcode)
limitNoResults for a name search, 1 to 20, default 5
barcodeNoEAN-8, UPC-A, EAN-13 or GTIN-14 digits (optional)

Output Schema

NameRequiredDescriptionDefault
countNo
queryNo
sourceNo
productsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint, but the description adds substantial operational context: an unknown barcode returns 404 and is not charged, community-sourced values can be missing or wrong, attribution is required under ODbL, and pricing is $0.002 per successful call via x402 across Base, Solana and other networks. That is exactly the payment/error/data-quality disclosure an agent needs before committing to a paid call.

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 access modes and the returned fields, then price, error and data-quality caveats in short trailing sentences — no filler. It is dense and somewhat long, and the field enumeration partially duplicates what the output schema already provides, keeping it just short of a 5.

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 paid, open-world lookup with an output schema, everything an agent needs is present: input modes and barcode formats, expected payload contents, 404-no-charge behavior, data-quality caveats, licensing attribution, and the exact payment model. Nothing material about invoking or paying for this tool is left unstated.

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 all three parameters (name, limit, barcode) are already documented, including the 2-100 character name range and the 1-20 limit default. The description restates the barcode formats and the barcode-or-name choice without adding constraints beyond the schema, so this is the baseline case of the schema doing the work.

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?

Names the resource (packaged food product data) and the two precise access modes (barcode formats EAN-8/UPC-A/EAN-13/GTIN-14, or product name), then enumerates exactly what is returned (brand, quantity, Nutri-Score, NOVA, nutrients per 100 g, allergens, labels, ingredients, image URL). An agent knows immediately this is a food product lookup and what it gets back, which no sibling tool overlaps with.

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 implied by the two-mode framing: supply a barcode, or a name when no barcode is available (the schema makes this explicit, the description only hints at it with 'or by name'). There is no explicit when-not guidance, no statement about which mode to prefer when both are known, and no routing to an alternative tool for a different kind of lookup.

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