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

Explain claim

explain_claim

Read-onlyIdempotent

Retrieve the primary sources, verification date and evidence gaps for a claim_id from an earlier result. Copy the exact ID; not a general question-answering tool.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`case_id`	No	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.
`claim_id`	Yes
`language`	No	Response language. Defaults to Chinese.	zh

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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"
+}

First observedJul 6, 2026

TDQS

A4.7/5.0

Behavior4/5

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

The annotations already declare readOnly, idempotent, and non-destructive behavior, and the description is consistent with them. The description adds useful behavioral context beyond the annotations: the tool is a focused evidence-gap lookup, not a free-form answer generator, and expects an exact carried-forward claim_id.

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 two short sentences with no filler. The retrieval purpose is front-loaded, and the critical ID-copying warning is placed at the end without repeating anything already in the annotations or schema.

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 simple read-only lookup with a detailed input schema, output schema, and strong annotations, this description is sufficient. It covers what the tool returns, where the input comes from, and how to use it correctly, leaving no important gap for an agent selecting or invoking it.

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?

The schema fully documents case_id and language, but claim_id only has length constraints. The description compensates by clarifying that claim_id must be the exact ID from an earlier result, not a natural-language question, which is essential semantic information for the required parameter.

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 description uses a specific verb ('Retrieve') and names concrete outputs: primary sources, verification date, and evidence gaps for a claim_id. It also explicitly distinguishes the tool from general question-answering, making its purpose and scope clear against the sibling tools.

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 tells the agent exactly when to use the tool: with a claim_id from an earlier result. It also gives an explicit when-not: this is not a general question-answering tool, and the ID must be copied exactly rather than paraphrased or invented.

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?