get_productBeauty product barcode lookup. Get detailed info for a cosmetics or personal care product by barcode (EAN/UPC) from Open Beauty Facts. Returns product name, brand, categories, ingredients, period-after-opening, labels, and image. Example: get_product("8001090662231") for a shampoo.
| Name | Required | Description | Default |
|---|---|---|---|
| barcode | Yes | Product barcode (EAN-13 or UPC-A, e.g., "8001090662231") |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "barcode": "8001090662231"
+ },
+ {
+ "barcode": "5010724526957"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds value beyond annotations by listing the specific fields returned (name, brand, categories, ingredients, etc.). Annotations already indicate it is read-only, non-destructive, and idempotent; no contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences plus an example, front-loaded with the action and source. Every sentence adds value with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter lookup tool with rich annotations and no output schema, the description adequately covers what data is returned. No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 100% coverage and describes the barcode parameter. The description adds example barcodes but does not provide additional semantic meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool is for beauty product barcode lookup, specifying the source (Open Beauty Facts) and the data returned (name, brand, categories, ingredients, etc.). It distinguishes itself from siblings like 'search_products' which likely does text-based search.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides a clear use case (barcode lookup) and an example, but does not explicitly state when not to use it or mention alternative tools for similar tasks.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.