Skip to main content
Glama

Trustbase Lab · Trusted Data Infrastructure for the AI Era

check_rcb_compliance

check_rcb_compliance
Read-onlyIdempotent

Purpose: rCB export-compliance checklist - PAH limits, SVHC obligations, food-contact rules and certification requirements for a given market and application. Guidelines: use for "can this rCB be sold in the EU / what PAH limits apply / what certifications do I need" questions; always state the application because the PAH limit differs (tire vs toy vs food-contact). Limits: distinguishes the REACH Annex XVII Entry 50 eight-PAH LIMIT list from the ECHA SVHC candidate-list PAH entries (notification duty) - these are different substance sets and must not be mixed; the stored limit values carry a "to be verified against EUR-Lex" note; this tool is not legal advice. Ex: check_rcb_compliance(market='EU', application='tire'), check_rcb_compliance(market='EU', application='toy').

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_rcb_compliance"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketNo目标市场EU
applicationNo应用场景;决定 PAH 限值档(轮胎 ≤1 / 玩具 ≤0.5 mg/kg 等)rubber_goods
response_formatNoOutput format: 'markdown' (default, human-readable) or 'json' (machine-readable).markdown

Output Schema

NameRequiredDescriptionDefault
textYesHuman-readable result (markdown, or a JSON string when response_format=json).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld=false, but the description adds substantive behavioral context they cannot: it warns that stored limit values carry a 'to be verified against EUR-Lex' note, that it is not legal advice, and that REACH Annex XVII Entry 50 eight-PAH limits must not be conflated with ECHA SVHC candidate-list entries. That is exactly the kind of interpretive constraint an agent needs before relaying results.

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?

Explicitly labeled Purpose / Guidelines / Limits / Ex sections make it scannable and front-loaded, with the most decision-relevant constraint (state the application) early. It is dense but nearly every clause carries decision value; the two near-identical examples are mildly redundant.

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 three-param, zero-required, read-only lookup with an output schema already defined, the description covers purpose, triggering questions, parameter-driven limit variation, domain caveats and legal disclaimers. Nothing an agent needs in order to call it correctly 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% with enums on all three params, so the baseline is 3; the description exceeds it by explaining that 'application' selects the applicable PAH limit tier (tire vs toy vs food-contact), which the schema only hints at, and by showing market+application pairs. It does not explain response_format, but that param is self-documenting.

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 opening line names a specific verb+resource ('rCB export-compliance checklist') and enumerates the exact domains covered: PAH limits, SVHC obligations, food-contact rules, certification requirements. It is immediately distinguishable from pricing/comparison siblings like compare_rcb or estimate_rcb_price.

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?

It gives verbatim user-intent triggers ('can this rCB be sold in the EU / what PAH limits apply / what certifications do I need') plus a mandatory usage rule ('always state the application because the PAH limit differs'), reinforcing it with two concrete call examples.

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