Skip to main content
Glama

clp_hazard_mixture_classifier

Read-onlyIdempotent

[CLP mixture health & aquatic hazard additivity classifier. Deterministic calculation, read-only, side-effect free]. Classifies chemical mixtures under Regulation (EC) No 1272/2008 (CLP) applying additivity formulas for skin/eye corrosion and summation methods with M-factors for environmental aquatic toxicity. Usage: Input mixture ingredients with concentration percentages and hazard classes to compute official GHS classifications and pictograms. Returns: JSON object with { mixtureTradeName: string, isHazardousMixture: boolean, governingSignalWord: string, resultingGhsClassifications: array, requiredGhsPictograms: array, mandatoryPrecautionaryStatements: 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": {
      "mixtureTradeName": "<mixtureTradeName>",
      "ingredients": "<ingredients>"
    },
    "name": "clp_hazard_mixture_classifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
ingredientsYesArray of mixture raw materials and active ingredients
mixtureTradeNameYesCommercial mixture brand or trade name
isAerosolOrSprayFormNoWhether the product is dispensed as aerosol/spray

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description's 'deterministic calculation, read-only, side-effect free' largely restates them, so no extra credit there. The genuine addition is the disclosure of the governing computation — CLP additivity formulas and summation methods with M-factors — which tells the agent the output is rule-derived and reproducible rather than heuristic. It stops short of noting limitations such as unsupported hazard endpoints or how unknown ingredients are handled.

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?

Front-loaded with the identity and regulatory basis, then cleanly segmented into Usage and Returns sections, which is easy for an agent to parse. Minor waste in the bracketed 'read-only, side-effect free' clause that duplicates annotations, and the Returns list is a dense inline dump rather than a tight summary, but overall it is well-proportioned.

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 compensates by enumerating the returned fields (isHazardousMixture, governingSignalWord, resultingGhsClassifications, requiredGhsPictograms, mandatoryPrecautionaryStatements), so the agent knows exactly what a call yields. Combined with the regulatory framing and the ingredient-input expectation, nothing essential for correct invocation is missing.

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 100%, so baseline is 3, and the description earns a notch above by explaining that M-factors participate in the aquatic summation method, giving the aquaticMFactor parameter operational meaning beyond its schema text. It also frames concentrationWeightPercent and hazardClassification as the drivers of the additivity calculation. It does not explain isAerosolOrSprayForm, which is defined only 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?

States a specific verb and resource ('CLP mixture health & aquatic hazard additivity classifier' / 'Classifies chemical mixtures under Regulation (EC) No 1272/2008') and names the underlying methods (additivity for skin/eye, summation with M-factors for aquatic). This is clearly distinguishable from the sibling clp_ufi_code_validator, which validates codes rather than computing mixture classifications.

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:' line tells the agent what to supply (ingredients with concentration percentages and hazard classes) to get GHS classifications and pictograms, which is decent input guidance. However, it gives no when-not-to-use conditions, no prerequisites, and never mentions that a single-substance/UFI lookup belongs to clp_ufi_code_validator instead. Usage is implied rather than bounded.

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