Skip to main content
Glama
Sign In

Openfoodfacts

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Country

country
Read-onlyIdempotent

Products from a country.

Input Schema

NameRequiredDescriptionDefault
pageNo
countryYes
page_sizeNo

Output Schema

NameRequiredDescriptionDefault
pageNoCurrent page number
countNoTotal products from country
productsNoArray of products from country
page_sizeNoResults per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country": "France"
+  },
+  {
+    "country": "United States",
+    "page": 1,
+    "page_size": 30
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total products from country",
+      "type": "number"
+    },
+    "page": {
+      "description": "Current page number",
+      "type": "number"
+    },
+    "page_size": {
+      "description": "Results per page",
+      "type": "number"
+    },
+    "products": {
+      "description": "Array of products from country",
+      "items": {
+        "properties": {
+          "brands": {
+            "description": "Brand names",
+            "type": "string"
+          },
+          "categories": {
+            "description": "Product categories",
+            "type": "string"
+          },
+          "code": {
+            "description": "Product barcode",
+            "type": "string"
+          },
+          "nova_group": {
+            "description": "NOVA group",
+            "type": "number"
+          },
+          "nutriscore_score": {
+            "description": "Nutri-Score value",
+            "type": "number"
+          },
+          "nutrition_grade_fr": {
+            "description": "Nutri-Score grade",
+            "type": "string"
+          },
+          "product_name": {
+            "description": "Product name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare this as a safe, idempotent read operation (readOnlyHint=true, idempotentHint=true, destructiveHint=false). The description adds no behavioral context beyond that, such as pagination behavior, data scoping, or limitations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but it is under-specified rather than efficiently concise. It reads as a title or label, not a functional tool description, and fails to earn its place by conveying necessary information.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the description leaves the tool's overall behavior, list semantics, and usage context unclear. With pagination parameters present, a one-line phrase is inadequate for a complete understanding.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not compensate. It merely repeats 'country' from the schema and leaves 'page' and 'page_size' completely unexplained. The description adds no meaning beyond the parameter names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Products from a country.' is a noun phrase without an explicit verb, so the operation (list, search, or get) is ambiguous. It identifies the resource (products) and a filter (country) but does not distinguish it from sibling tools like 'product' or 'category'.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool vs alternatives. There is no mention of use cases, prerequisites, or relationships to sibling tools such as 'brand', 'category', or 'search'.

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

All Openfoodfacts toolsInspect
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