Skip to main content
Glama

food_contact_materials_fcm_screener

Read-onlyIdempotent

[Food contact materials (FCM) overall & specific migration limit screener. Deterministic calculation, read-only, side-effect free]. Evaluates food contact material compliance under Regulation (EC) No 1935/2004 and Regulation (EU) No 10/2011, checking overall migration limit (10 mg/dm²), specific migration limits (SML), and simulant coverage. Usage: Pass material type, food category, migration test measurements, and Declaration of Compliance status to audit food safety. Returns: JSON object with { materialTradeName: string, overallMigrationLimitCheck: object, specificMigrationAudit: object, simulantsSuitabilityCheck: object, statutoryVerdict: string, nonComplianceReasons: array, docRequirementsMet: boolean }.

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": {
      "materialTradeName": "<materialTradeName>",
      "materialType": "<materialType>",
      "intendedFoodCategory": "<intendedFoodCategory>",
      "maximumContactTemperatureCelsius": "<maximumContactTemperatureCelsius>",
      "contactDurationHours": "<contactDurationHours>",
      "overallMigrationMgPerDm2": "<overallMigrationMgPerDm2>",
      "testedWithFoodSimulants": "<testedWithFoodSimulants>",
      "declarationOfComplianceIssued": "<declarationOfComplianceIssued>",
      "containsRecycledPlasticReg2022_1616": "<containsRecycledPlasticReg2022_1616>"
    },
    "name": "food_contact_materials_fcm_screener"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialTypeYesChemical and structural classification of the contact material
materialTradeNameYesCommercial name or trade reference of the food packaging material
contactDurationHoursYesMaximum foreseeable contact duration in hours
intendedFoodCategoryYesNature of foodstuffs intended to come into contact with the material
testedWithFoodSimulantsYesFood simulants used in laboratory migration tests ex Annex III
overallMigrationMgPerDm2YesMeasured Overall Migration in mg/dm² (statutory limit: 10.0 mg/dm²)
specificSubstancesMigrationNoSubstances subject to Specific Migration Limits (SML)
declarationOfComplianceIssuedYesWhether written Declaration of Compliance (DoC) ex Article 16 is issued
maximumContactTemperatureCelsiusYesHighest intended contact temperature in degrees Celsius (e.g. 100°C for boiling/hot fill)
containsRecycledPlasticReg2022_1616YesIf plastic contains recycled content, whether process is certified under Regulation (EU) 2022/1616

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so 'deterministic calculation, read-only, side-effect free' largely restates structured data. However, the description adds real behavioral context the annotations cannot: the exact statutory regimes applied, the 10 mg/dm² threshold, the three audit dimensions performed, and the shape of the returned verdict object in the absence of an output schema.

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 definition is front-loaded with a bracketed scope tag, then a purpose sentence, a Usage line, and a Returns line — an easy structure to scan. The bracketed preamble partly duplicates the annotations, and the Returns enumeration is dense, but nothing is genuinely extraneous.

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 10-parameter, 9-required compliance tool with no output schema, the description compensates well by listing the return fields and the regulatory basis. Remaining gaps are minor: it does not explain allowed values for statutoryVerdict, the content of nonComplianceReasons, or whether specificSubstancesMigration is optional in practice.

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% and every parameter, including both enums and the nested SML substance object, is already documented in the schema. The description's usage sentence only names parameter groups (material type, food category, measurements, DoC status) without adding format, units, or validation semantics beyond what the schema states.

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 names a specific verb+resource ('Food contact materials (FCM) ... migration limit screener') and enumerates exactly what it evaluates: overall migration limit (10 mg/dm²), specific migration limits (SML), and simulant coverage under Regulations 1935/2004 and 10/2011. It is far more specific than a generic compliance checker, but it never distinguishes itself from chemically adjacent siblings such as reach_svhc_threshold_screener or clp_hazard_mixture_classifier.

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?

'Usage: Pass material type, food category, migration test measurements, and Declaration of Compliance status to audit food safety' describes required inputs rather than when to choose this tool over alternatives. There is no statement of when not to use it, no prerequisite (e.g. lab test results must exist first), and no routing to a sibling tool for non-FCM chemical checks.

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