Skip to main content
Glama
Sign In

Openfoodfacts

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Brand

brand
Read-onlyIdempotent

Products by brand.

Input Schema

NameRequiredDescriptionDefault
pageNo
brandYes
page_sizeNo

Output Schema

NameRequiredDescriptionDefault
pageNoCurrent page number
countNoTotal products by brand
productsNoArray of products by brand
page_sizeNoResults per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "brand": "Coca-Cola"
+  },
+  {
+    "brand": "Nestlé",
+    "page": 1,
+    "page_size": 25
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total products by brand",
+      "type": "number"
+    },
+    "page": {
+      "description": "Current page number",
+      "type": "number"
+    },
+    "page_size": {
+      "description": "Results per page",
+      "type": "number"
+    },
+    "products": {
+      "description": "Array of products by brand",
+      "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

C2.8/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds no extra behavioral details such as pagination behavior, sorting, or return format. It does not contradict annotations but also provides no value beyond them.

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?

The description is a single short phrase, 'Products by brand,' with zero unnecessary words. It is front-loaded with the core noun 'Products' and immediately states the filtering dimension. The extreme brevity is a positive trait for conciseness, though it sacrifices detail captured in other dimensions.

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?

Given there is an output schema and annotations, the description has some support. However, it fails to elaborate on pagination or the nature of the returned product list. For a tool with three parameters, this minimal description leaves significant gaps in usage understanding, especially since no alternative guidance is provided.

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%, so the description must compensate by explaining the parameters. It only hints at 'brand' through the tool name and description, but does not explain 'page' or 'page_size' at all. While page and page_size are conventional, their semantics are not explicitly defined in either the schema or description.

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?

The description 'Products by brand' clearly communicates that this tool returns products filtered by a specific brand, distinguishing it from similar tools like 'category' or 'product'. However, it lacks an explicit verb (such as 'list' or 'get'), making it a noun phrase rather than a full action statement.

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?

There is no guidance on when to use this tool versus alternatives. The sibling tools 'category' and 'product' suggest related functionality, but the description provides no context for selecting 'brand' over them. No exclusions or comparisons are given.

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