openfoodfacts-mcp-server

get_eco_score

Retrieve the Eco-Score and environmental impact of a food product using its barcode, including CO2 footprint, packaging, origin, and rating.

Instructions

Ruft den Eco-Score und Umweltinformationen eines Produkts ab. Gibt CO2-Fussabdruck, Verpackung, Herkunft und Umweltbewertung zurueck.

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

Input Schema

Name	Required	Description	Default
`barcode`	Yes	EAN-Barcode des Produkts

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the output fields but does not mention any side effects, authentication needs, rate limits, or whether the operation is read-only. For a simple query tool, this is adequate but lacks depth.

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?

Two sentences, front-loaded with purpose, no wasted words. Efficient and easy to parse.

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?

Given the tool has a single parameter, no annotations, and an output schema (exists but not shown), the description provides sufficient context about what the tool returns. However, it could mention that it is a read operation or reference the output schema. Still, it is reasonably complete.

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% for the single 'barcode' parameter. The description does not add any additional meaning or context beyond what the schema already provides (EAN-Barcode des Produkts).

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 states exactly what the tool does: retrieving Eco-Score and environmental information of a product, listing specific output fields (CO2 footprint, packaging, origin, environmental rating). This clearly distinguishes it from sibling tools like get_nutrition_facts or get_product_labels.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. The description does not mention when not to use it or provide context for selection among sibling tools.

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

Deploy Server