ComplianceCN — toys, batteries, cosmetics, food contact: CE, GPSR, UN 38.3, CPC/GCC and more

Compare markets

compare_market_requirements

Read-onlyIdempotent

Compare requirements for a product across 2-4 of EU, UK, US and Australia. Answers immediately: no case, no account, no follow-up. Send category, markets and known facts. Missing facts produce optional refinements; do not ask or rerun automatically.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`case_id`	No	The case this call continues, from an earlier result. Omit to start a new product case.
`markets`	Yes
`category`	Yes	Product category
`language`	No	Response language. Defaults to Chinese.	zh
`age_group`	No	Intended user age. Decides whether toy safety rules apply and which small-parts and warning duties follow.
`food_type`	No	The food the product will contact. Simulant selection for migration testing depends on it.
`has_radio`	No	Whether the product transmits: Bluetooth, Wi-Fi, NFC, or any other radio. Decides the RED conformity route in the EU and FCC authorisation in the US.
`has_battery`	No	Whether the product contains or ships with any battery, including a coin cell in a remote.
`battery_type`	No	Cell chemistry. Decides whether UN 38.3 transport testing and battery-passport duties apply. Use unknown rather than guessing.
`is_sunscreen`	No	Whether the product is sold as sun protection. Sunscreens carry separate testing and labelling duties.
`repeated_use`	No	Whether the article is single-use or reused. Repeated use requires migration testing across successive cycles.
`verified_only`	No	Exclude rules not yet checked against primary sources. Default false: unverified material is included but labelled via review_status and the trust envelope.
`eu_destination`	No	Destination member state, where it changes the answer. Language and producer-registration duties differ across the EU.
`contact_duration`	No	How long the product touches food in normal use. Long-term contact triggers stricter migration testing.
`supply_chain_role`	No	The seller's role in the chain. Decides which duties are theirs rather than the manufacturer's or importer's.
`claims_therapeutic`	No	Whether the product claims to treat, prevent or cure anything. A therapeutic claim moves a cosmetic into a different regime.
`contact_temperature`	No	The temperature at contact. Hot fill and cooking raise migration limits and change the test.
`ingredients_reviewed`	No	Whether the full ingredient list has already been checked against restricted-substance annexes.
`is_childrens_product`	No	Whether the product is marketed as a children's product; keep unknown when not established.
`food_contact_material`	No	The material that touches food. Migration limits and test methods differ by material.
`accessible_small_parts`	No	Whether a child could reach a part that fits in a small-parts cylinder, including parts freed by reasonably foreseeable use.
`includes_mains_charger`	No	Whether a mains plug, wall charger or power adapter ships in the box. A supplied charger is separately in scope.
`is_electrically_operated`	No	Whether the toy is electrically operated, including mains-powered or battery-powered operation.
`battery_compartment_security`	No	How the battery compartment is secured. Button and coin cells carry stricter duties because ingestion is the hazard.
`toy_chemical_assessment_complete`	No	Whether a chemical safety assessment covering migration limits has already been completed for this toy.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`payload`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedAug 22, 2026

addedInput schema / properties / accessible_small_parts / description

Added value: +"Whether a child could reach a part that fits in a small-parts cylinder, including parts freed by reasonably foreseeable use."

addedInput schema / properties / age_group / description

Added value: +"Intended user age. Decides whether toy safety rules apply and which small-parts and warning duties follow."

addedInput schema / properties / battery_compartment_security / description

Added value: +"How the battery compartment is secured. Button and coin cells carry stricter duties because ingestion is the hazard."

addedInput schema / properties / battery_type / description

Added value: +"Cell chemistry. Decides whether UN 38.3 transport testing and battery-passport duties apply. Use unknown rather than guessing."

changedInput schema / properties / case_id / description

Previous value: -"Opaque ComplianceCN product-case ID returned by the first successful free workflow call. Carry it unchanged through clarification retries, Stage 2 and human review for the same product/SKU. Never reuse it for another product or SKU."New value: +"The case this call continues, from an earlier result. Omit to start a new product case."

addedInput schema / properties / claims_therapeutic / description

Added value: +"Whether the product claims to treat, prevent or cure anything. A therapeutic claim moves a cosmetic into a different regime."

addedInput schema / properties / contact_duration / description

Added value: +"How long the product touches food in normal use. Long-term contact triggers stricter migration testing."

addedInput schema / properties / contact_temperature / description

Added value: +"The temperature at contact. Hot fill and cooking raise migration limits and change the test."

addedInput schema / properties / eu_destination / description

Added value: +"Destination member state, where it changes the answer. Language and producer-registration duties differ across the EU."

addedInput schema / properties / food_contact_material / description

Added value: +"The material that touches food. Migration limits and test methods differ by material."

addedInput schema / properties / food_type / description

Added value: +"The food the product will contact. Simulant selection for migration testing depends on it."

addedInput schema / properties / has_battery / description

Added value: +"Whether the product contains or ships with any battery, including a coin cell in a remote."

addedInput schema / properties / has_radio / description

Added value: +"Whether the product transmits: Bluetooth, Wi-Fi, NFC, or any other radio. Decides the RED conformity route in the EU and FCC authorisation in the US."

addedInput schema / properties / includes_mains_charger / description

Added value: +"Whether a mains plug, wall charger or power adapter ships in the box. A supplied charger is separately in scope."

addedInput schema / properties / ingredients_reviewed / description

Added value: +"Whether the full ingredient list has already been checked against restricted-substance annexes."

addedInput schema / properties / is_sunscreen / description

Added value: +"Whether the product is sold as sun protection. Sunscreens carry separate testing and labelling duties."

addedInput schema / properties / repeated_use / description

Added value: +"Whether the article is single-use or reused. Repeated use requires migration testing across successive cycles."

changedInput schema / properties / supply_chain_role / description

Previous value: -"Supply-chain role. Canonical values are manufacturer, importer, distributor, marketplace_seller or unknown. Common natural-language English and Chinese labels are accepted and normalized."New value: +"The seller's role in the chain. Decides which duties are theirs rather than the manufacturer's or importer's."

addedInput schema / properties / toy_chemical_assessment_complete / description

Added value: +"Whether a chemical safety assessment covering migration limits has already been completed for this toy."

Changed1 schema field changedJul 28, 2026

addedInput schema / properties / case_id

Added value: +{
+  "description": "Opaque ComplianceCN product-case ID returned by the first successful free workflow call. Carry it unchanged through clarification retries, Stage 2 and human review for the same product/SKU. Never reuse it for another product or SKU.",
+  "pattern": "^ccase_[a-f0-9]{24}$",
+  "type": "string"
+}

Changed5 schema fields changedJul 28, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "toys",
-  "battery-electronics",
-  "cosmetics",
-  "food-contact"
-]New value: +[
+  "battery-electronics",
+  "toys",
+  "cosmetics",
+  "food-contact",
+  "toy",
+  "玩具",
+  "battery",
+  "electronics",
+  "电池电子产品",
+  "带电池电子产品",
+  "cosmetic",
+  "化妆品",
+  "food_contact",
+  "foodcontact",
+  "食品接触材料",
+  "食品接触用品",
+  "食品接触产品"
+]

addedInput schema / properties / supply_chain_role / description

Added value: +"Supply-chain role. Canonical values are manufacturer, importer, distributor, marketplace_seller or unknown. Common natural-language English and Chinese labels are accepted and normalized."

removedInput schema / properties / supply_chain_role / enum

Removed value: -[
-  "manufacturer",
-  "importer",
-  "distributor",
-  "marketplace_seller",
-  "unknown"
-]

addedInput schema / properties / supply_chain_role / maxLength
```
Added value: +80
```
addedInput schema / properties / supply_chain_role / minLength
```
Added value: +1
```

Changed2 schema fields changedJul 16, 2026

addedInput schema / properties / is_childrens_product

Added value: +{
+  "description": "Whether the product is marketed as a children's product; keep unknown when not established.",
+  "type": "boolean"
+}

addedInput schema / properties / is_electrically_operated

Added value: +{
+  "description": "Whether the toy is electrically operated, including mains-powered or battery-powered operation.",
+  "type": "boolean"
+}

Changed2 schema fields changedJul 9, 2026
- addedInput schema / properties / contact_duration
```
Added value: +{
+  "maxLength": 80,
+  "type": "string"
+}
```
- addedInput schema / properties / food_type
```
Added value: +{
+  "maxLength": 80,
+  "type": "string"
+}
```
First observedJul 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false so the safety profile is known. The description adds significant interaction context beyond the annotations: 'Answers immediately: no case, no account, no follow-up' and 'Missing facts produce optional refinements; do not ask or rerun automatically.' This explains the tool's autonomy and output behavior without contradicting any annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three short sentences with no filler. Each sentence earns its place: the first states the core action, the second sets interaction expectations, and the third gives invocation guidance and the missing-facts behavior. The critical behavioral note is placed immediately after the action, making it easy to parse.

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 tool with 25 parameters and an output schema, the description covers the essential invocation requirements and the tool's autonomous behavior. It does not detail the output structure, but the output schema exists and carries that load. The concept of 'optional refinements' is not elaborated, but it is enough to set expectations. The description is sufficient for an agent to call the tool correctly with the right inputs.

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 96%, so the schema thoroughly documents each of the 25 parameters. The description only highlights the two required parameters ('category, markets') and the general notion of 'known facts', adding minimal semantic detail beyond the schema. The mention of 'optional refinements' hints at how missing parameters are handled, but that is behavioral rather than parameter-specific.

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 clearly states the action ('Compare requirements for a product') and explicitly defines the scope ('across 2-4 of EU, UK, US and Australia'). This distinguishes it from sibling tools that focus on single-region or single-issue checks, though it does not name those tools. The title 'Compare markets' is less precise but the description itself is specific enough.

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 description instructs the agent to 'Send category, markets and known facts', which is a clear directive for invocation. It also warns that missing facts produce optional refinements and that the tool will not ask or rerun automatically. However, it does not explicitly state when to choose this tool over sibling tools like check_label_and_packaging or market_access_check, nor does it mention any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ComplianceCN — toys, batteries, cosmetics, food contact: CE, GPSR, UN 38.3, CPC/GCC and more tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?