Skip to main content
Glama
Jatin-IITB

Open Food Facts MCP Server

by Jatin-IITB

searchProducts

Search for food products by name, brand, or category to access nutritional information and product details.

Instructions

Search products by name, brand, or category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
pageNo
pageSizeNo
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the search purpose without mentioning pagination behavior, authentication needs, or result limitations. This is inadequate for a tool with no annotation coverage.

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?

The description is very concise at 6 words, but it misses critical information like pagination and parameter details. While not verbose, it is under-specified, which reduces its effectiveness for an AI agent.

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 the tool has 3 parameters, no output schema, and many sibling tools, the description is incomplete. It fails to explain how it differs from other search tools, does not describe the return format, and omits pagination behavior.

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 should add meaning beyond parameter names. It mentions query by name/brand/category but ignores page and pageSize parameters, which are not self-explanatory in terms of their purpose and defaults.

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 clearly states the tool searches products by name, brand, or category, providing a specific verb and resource. However, it does not differentiate from sibling tools like searchByBrand or searchByCategory, which are more targeted.

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?

The description offers no guidance on when to use this tool versus alternatives. With 20 sibling tools including advancedSearch and specific brand/category searches, the lack of usage context is a significant gap.

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/openbeautyfacts-mcp'

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