Skip to main content
Glama
Jatin-IITB

Open Food Facts MCP Server

by Jatin-IITB

searchByBrand

Locate all products from a specified brand, returning nutritional and ingredient data.

Instructions

Find all products from a specific brand

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandYesBrand name to search for
pageNo
pageSizeNo
Behavior2/5

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

No annotations provided, and the description fails to disclose behavioral traits such as pagination, limits, or side effects. For a search tool, it is excessively minimal.

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

Conciseness4/5

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

Single sentence is concise and front-loaded, but could be more structured to include key details like pagination behavior.

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 no annotations, no output schema, and low parameter description coverage, the description is incomplete. It does not mention output format or pagination details.

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 33%, with only 'brand' having a description. The description does not explain 'page' or 'pageSize' beyond what the schema provides, failing to compensate for low coverage.

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?

Description clearly states 'Find all products from a specific brand', using a specific verb and resource. It distinguishes from sibling tools like searchByCategory and searchProducts.

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 guidance on when to use this tool versus alternatives. The sibling list includes many similar search tools, but the description lacks context or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jatin-IITB/openproductsfacts-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server