Skip to main content
Glama

AutoTasker Hub — China Social Data API

openfoodfacts

Food product lookup by barcode: name, brand, Nutri-Score, NOVA group, allergens, per-100g nutrients. $0.01 USDC.

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

Input Schema

NameRequiredDescriptionDefault
barcodeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose a real behavioral trait that structured fields don't capture – the $0.01 USDC cost per call – but says nothing about error handling for invalid barcodes, whether payment/auth is required up front, coverage limitations of the database, or response shape beyond the field list.

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?

A single compact sentence, front-loaded with the verb and resource and followed by the payload fields and price. Every fragment earns its place; nothing is redundant with the schema.

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?

The tool is simple (one required string, no nested objects, no output schema), and the description compensates for the missing output schema by naming the returned fields. However, for a paid call with no annotations, the absence of any note on invalid-barcode behavior or database scope leaves a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single parameter, so the description must compensate. It only restates that the input is a barcode; it adds no format guidance (numeric vs. EAN-13/UPC length, leading zeros), no example, and no indication of what a malformed value does.

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?

States a specific verb and resource ('Food product lookup by barcode') and enumerates the returned fields (name, brand, Nutri-Score, NOVA group, allergens, per-100g nutrients), so the agent knows exactly what it gets. No sibling in the catalog overlaps with food-product lookup, so no differentiation sentence is required, but none is offered.

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 phrase 'by barcode' tells the agent the required input, from which when-to-use follows naturally. There is no explicit statement of when to prefer this tool over alternatives, no note on what happens with an unknown or non-food barcode, and no exclusions.

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.