Skip to main content
Glama

Check a food additive, colour, novel food or food contact substance

regaffairs_check_food_additive_or_ingredient
Read-onlyIdempotent

Checks whether a food additive (E-number), colour additive, novel food, vitamin or mineral form, food contact substance or contaminant limit is allowed, and under which conditions, in the EU or US. EU coverage: Regulation (EC) No 1333/2008 Annex II with food categories and maximum levels, the Novel Food Union list (Regulation 2015/2283), contaminant maximum levels (Regulation 2023/915), the food supplements Directive 2002/46/EC and fortified foods Regulation 1925/2006, the plastics food contact Union list (Regulation 10/2011), the German BfR food contact recommendations, and EFSA scientific opinions. US coverage: 21 CFR Parts 170 to 189, FDA GRAS notices, the FDA substances added to food inventory, colour additives in 21 CFR Parts 73 and 74 and the FDA colour additive status list, food contact notifications and indirect additives. Not intended for labelling, allergen or health claim questions (regaffairs_check_food_label_and_allergens covers those) or pesticide residues (regaffairs_check_pesticide_approval_and_mrl).

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": {
      "ingredient": "<ingredient>"
    },
    "name": "regaffairs_check_food_additive_or_ingredient"
  }
}

Input Schema

NameRequiredDescriptionDefault
regimeNoany
ingredientYesName, E-number (e.g. E171), INS number, FD&C name (e.g. Red No. 3) or CAS.
food_categoryNoOptional, e.g. 'flavoured drinks', 'confectionery' or EU category 14.1.4.
jurisdictionsNo
contact_materialNoFor food contact questions.

Output Schema

NameRequiredDescriptionDefault
resultsYes
sourcesYes
not_foundYes
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuine behavioral context beyond that: the exact regulatory corpus consulted (1333/2008 Annex II, 2015/2283, 2023/915, 10/2011, 21 CFR 170-189, GRAS notices) and that results are jurisdiction- and category-conditional. It does not discuss latency, rate limits, or answer-completeness caveats.

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 purpose sentence is front-loaded and efficient, but the middle is a dense, unbroken enumeration of regulations that reads more like documentation than selection guidance. It is informative yet disproportionately long relative to the decision it supports, and the exclusions would be easier to scan if split out from the coverage dump.

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

Completeness4/5

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

For a complex multi-jurisdiction regulatory lookup with 5 parameters, an output schema, and rich annotations, the description supplies the domain scope, jurisdiction coverage and sibling boundaries an agent needs. It is nearly complete; only the meaning of the 'any' regime default and how multiple jurisdictions combine in the response are left to the schema/output.

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

Parameters4/5

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

Schema coverage is 60%, so the description must carry part of the load, and it does: the coverage list maps directly onto the regime enum values (food_additive, colour_additive, novel_food, supplement_or_fortification, food_contact, contaminant, gras), 'EU or US' explains the jurisdictions array, and 'food categories and maximum levels' and 'plastics food contact' imply food_category and contact_material usage. It does not spell out the 'any' default or the accepted input formats beyond the schema's own E-number/INS/FD&C/CAS note.

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 precise verb ('Checks whether... is allowed') and enumerates the exact resource classes covered (food additive E-number, colour additive, novel food, vitamin/mineral, food contact substance, contaminant limit) across two jurisdictions. It also names the siblings it is NOT, so an agent can separate it from regaffairs_check_food_label_and_allergens and regaffairs_check_pesticide_approval_and_mrl without opening a schema.

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

Usage Guidelines5/5

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

Explicit when-not guidance is present with named alternatives: 'Not intended for labelling, allergen or health claim questions (regaffairs_check_food_label_and_allergens covers those) or pesticide residues (regaffairs_check_pesticide_approval_and_mrl).' Combined with the positive statement of scope (EU or US, allowed and under which conditions), the routing decision is fully determined.

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.

Resources