Skip to main content
Glama

rohs_substance_limit_checker

Read-onlyIdempotent

[RoHS 3 restricted substance limit checker & technical exemption auditor. Deterministic calculation, read-only, side-effect free]. Verifies homogeneous material compliance under Directive 2011/65/EU and Delegated Directive 2015/863 across 10 restricted heavy metals and phthalates, auditing Annex III/IV technical exemptions. Usage: Pass measured ppm values for homogeneous materials with optional exemption codes (e.g. '6c' for lead in copper alloys). Returns: JSON object with { homogeneousMaterialName: string, isRoHsCompliant: boolean, passCount: number, failCount: number, evaluations: 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": {
      "homogeneousMaterialName": "<homogeneousMaterialName>",
      "testedSubstances": "<testedSubstances>"
    },
    "name": "rohs_substance_limit_checker"
  }
}

Input Schema

NameRequiredDescriptionDefault
testedSubstancesYesArray of substance concentration measurements
homogeneousMaterialNameYesHomogeneous material identifier (e.g. Copper Alloy C36000, PVC Cable Sheath)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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, read-only, side-effect free' is largely redundant restatement. The description does add value beyond the annotations by disclosing the regulatory basis of the calculation, the fact that exemptions materially alter the verdict, and the exact response envelope (compliance boolean, pass/fail counts, per-substance evaluations).

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-loads the tool's identity and scope before the Usage and Returns blocks, and the bracketed preamble is the only clear waste since read-only/deterministic is already in the annotations. Otherwise dense with no filler sentences.

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?

For a two-parameter calculator with no output schema, the description supplies everything needed: the regulatory framework, the substance coverage, the exemption mechanism, and the return structure. Nothing required to call it correctly or interpret the result is missing.

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%, with the enum of ten substance keys and per-field descriptions already documented. The description only echoes the semantics already present ('measured ppm values', 'optional exemption codes') and adds no constraint the schema lacks, so the 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?

States a specific verb and resource ('restricted substance limit checker', 'verifies homogeneous material compliance under Directive 2011/65/EU and Delegated Directive 2015/863') with named scope (10 heavy metals and phthalates) and a distinct secondary function (Annex III/IV exemption auditing). An agent can distinguish this from tangential compliance siblings such as clp_hazard_mixture_classifier or construction_materials_cpr_audit on the basis of the RoHS directive alone.

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 explains how to invoke it (pass measured ppm values per homogeneous material, optional exemption codes such as '6c' for lead in copper alloys), which implies the applicable scenario. However, it never states when to choose this tool over an adjacent compliance checker, nor any exclusion such as non-homogeneous or article-level assessment, leaving routing to inference.

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