Skip to main content
Glama

Check a product for allergens

check_product_allergens
Read-onlyIdempotent

Check a product's ingredient list against the allergies of one or more people in a household. Catches allergens listed under other names (e.g. "arachis oil" for peanut, "casein" for milk, Latin plant names in cosmetics) and does not let "free from" claims hide a real ingredient. Covers food and cosmetics. Use when the user asks if a product or ingredient list is safe for someone with allergies. A result with no listed allergens is not a promise of safety: relay the limits, and never call the product "safe".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ingredients": "<ingredients>",
      "household": "<household>"
    },
    "name": "check_product_allergens"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the text, if known, e.g. "fr". Optional; helps short words in other languages be read correctly.
householdYesOne entry per person, each with their allergens.
ingredientsYesThe product's ingredient list, or the product page text that contains it.
product_nameNoProduct name, for the answer only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Language of the text, if known, e.g. \"fr\". Optional; helps short words in other languages be read correctly.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral context: it matches synonyms and Latin names, deliberately disregards 'free from' claims, spans food and cosmetics, and warns that an empty result is not proof of safety. The instruction never to call a product 'safe' is exactly the kind of caveat annotations cannot express.

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?

It is front-loaded with the core action, followed by detection behavior, then the usage trigger, then the safety caveat. Four tight sentences with no repetition of the title or name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description still tells the agent what a result means and how to communicate it (relay the limits, never assert safety). Combined with full schema coverage and annotations, an agent has everything needed to call this correctly and report honestly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents language, household, ingredients, and product_name. The description reinforces the household concept ('one or more people') and the ingredient-list input, but adds no parsing or format guidance beyond what the schema supplies; baseline 3 applies.

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?

The description states a specific verb and resource — checking a product's ingredient list against a household's allergens — and immediately frames the scope (food and cosmetics, synonym matching, ignoring 'free from' claims). It is clearly distinguishable from lookup_ingredient and list_supported_allergens, which are single-item/registry helpers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger: 'Use when the user asks if a product or ingredient list is safe for someone with allergies.' What is missing is an explicit inverse or alternative — it never says when to prefer lookup_ingredient or list_supported_allergens, so routing is only implied for the siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.