Skip to main content
Glama

FIC Food Allergen Highlighting & Big 7 Nutrition Table Deterministic Screener

food_allergen_nutrition_label_screener
Read-onlyIdempotent

[FIC food allergen highlighting & Big 7 nutrition table deterministic screener. Pure calculation, read-only, side-effect free]. Audits food packaging labels against Regulation (EU) No 1169/2011 (FIC), detecting 14 Annex II allergens, checking font x-height legibility (1.2mm / 0.9mm), and auditing mathematical consistency of the mandatory Big 7 nutrition table. Usage: Pass product name, ingredient list, declared allergens, and nutrition table values to verify packaging compliance. Returns: JSON object with { productName: string, mandatoryAllergenAudit: object, nutritionTableAudit: object, legibilityAudit: object, statutoryVerdict: string, nonComplianceFindings: array }.

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": {
      "productName": "<productName>",
      "ingredientList": "<ingredientList>",
      "declaredAllergens": "<declaredAllergens>",
      "nutritionPer100gOrMl": "<nutritionPer100gOrMl>",
      "fontXHeightMm": "<fontXHeightMm>",
      "packagingLargestSurfaceAreaCm2": "<packagingLargestSurfaceAreaCm2>",
      "allergensDistinguishedInIngredients": "<allergensDistinguishedInIngredients>"
    },
    "name": "food_allergen_nutrition_label_screener"
  }
}

Input Schema

NameRequiredDescriptionDefault
productNameYesCommercial food product name
fontXHeightMmYesMeasured x-height of packaging label typography in millimeters
ingredientListYesFull ingredient text as printed on packaging
declaredAllergensYesAllergens explicitly highlighted or listed in allergen box
nutritionPer100gOrMlYesMandatory Big 7 nutrition values per 100g or 100ml
packagingLargestSurfaceAreaCm2YesSurface area of the largest packaging face in cm² (threshold: 80 cm²)
allergensDistinguishedInIngredientsYesWhether allergens in ingredients list are emphasized through a distinct typeset (Art. 21(1)(b))

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description nonetheless reinforces 'pure calculation, side-effect free' and, more usefully, discloses the deterministic rule set being applied (1.2mm/0.9mm x-height, mathematical consistency of the Big 7 table). It also sketches the response shape even though no output schema exists, which is real added value for a calculation tool.

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?

The structure is well front-loaded: scope and safety profile first, then usage, then return shape. The opening bracketed sentence partially duplicates the title, which is minor waste, but the remaining sentences are dense and earn their place.

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 seven-parameter tool with a nested object and no output schema, the description covers the three audit domains it performs and compensates for the missing output schema by listing the returned keys. What remains thin is the relationship between inputs and findings — how a statutory verdict is derived — but the essentials for correct invocation are present.

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 fully documents all seven parameters including the nested nutrition object, and the baseline of 3 applies. The description adds only the thresholds (0.9/1.2mm, 80 cm²) that give the numeric inputs meaning; otherwise it simply names the inputs already described in the schema.

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 — auditing food packaging labels — and pins the exact legal basis (Regulation (EU) No 1169/2011), the 14 Annex II allergens, the x-height thresholds, and the Big 7 table check. That level of specificity clearly separates it from the other regulatory screeners in the sibling list, notably food_contact_materials_fcm_screener, which covers a different regime.

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

Usage Guidelines3/5

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

The 'Usage' sentence gives a context (verify packaging compliance) but it is essentially a restatement of the required inputs rather than guidance on when to choose this tool over an alternative. There are no exclusions, no prerequisites, and no routing to a sibling for adjacent questions such as FCM migration or CLP hazard classification.

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