Skip to main content
Glama
Open Food Facts MCP

Open Food Facts MCP

by MrBridgeHQ

search_products

Read-onlyIdempotent

Find Open Food Facts products by brand, category, country, language, Nutri-Score, and pagination filters to retrieve matching food items.

Instructions

Search Open Food Facts products with documented taxonomy filters.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
brandNo
countryNo
categoryNo
languageNo
page_sizeNo
nutriscoreNo

Output Schema

NameRequiredDescriptionDefault
dataYes
sourceYes
warningsYes
cache_hitYes
retrieved_atYes
missing_fieldsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no note on pagination behavior, result caps (page_size max 20, page max 1000), or that taxonomy values must be resolved first.

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

Conciseness3/5

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

A single short sentence with no padding and a clear front-loaded verb, but the brevity is under-specification rather than efficiency given the 7-parameter surface. It is structurally fine but leaves too much unsaid.

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?

An output schema and annotations exist, so return values and safety need not be described, but for a 7-parameter search with zero schema descriptions and no sibling differentiation the definition is materially incomplete. It omits filter semantics, pagination behavior, and the relationship to get_taxonomy.

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% across 7 parameters, so the description carries the full burden, yet it only alludes to 'taxonomy filters' generically. It never maps that phrase to brand/country/category, nor explains the regex/format constraints, page/page_size limits, or the nutriscore enum, leaving most parameters undocumented anywhere.

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

Purpose3/5

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

The verb and resource are clear ('Search Open Food Facts products'), which is better than a tautology, but 'with documented taxonomy filters' is vague and does not distinguish this tool from the sibling search_text or get_taxonomy. An agent cannot tell from the description which search entry point to pick.

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 when-to-use guidance, no exclusions, and no mention of the sibling tools (search_text, get_product, compare_products). The phrase 'documented taxonomy filters' hints that filters must come from a taxonomy, but never says to call get_taxonomy first to obtain valid values.

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