Skip to main content
Glama

CN Evidence

by dev.workers.mikeyang7789.cn-evidence-mcp-public
OverviewDiscussionsAdmin

get_china_supplier_evidence_full

0.093 USDC via x402 on Base. Nine supplier information modules; selected current status and first page up to 10 records per list. No historical expansion or automatic paging. Not complete due diligence. Requires an x402 v2 payment client, a funded Base USDC wallet and spending authorization; a plain MCP connection alone cannot purchase data. Use an exact Chinese legal name or USCC, not a guessed English-name match. Setup and free fictional sample: https://yangchunhong3000.github.io/cn-evidence-public-docs/buyer-guide.html Optional 24h report recovery requires a saved random 32-byte hex X-CN-Recovery-Token header on the paid request, then a free POST to https://api.cnevidence.com/free/cn/payment/recover. See guide; never automatically repay after a timeout.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / $defs / FullEvidenceRequest
      Removed value: -{
-  "properties": {
-    "company": {
-      "anyOf": [
-        {
-          "maxLength": 200,
-          "minLength": 2,
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Chinese legal company or supplier name.",
-      "title": "Company"
-    },
-    "evidence_limit": {
-      "default": 100,
-      "description": "Maximum detailed evidence rows to return.",
-      "maximum": 100,
-      "minimum": 0,
-      "title": "Evidence Limit",
-      "type": "integer"
-    },
-    "include_evidence": {
-      "default": true,
-      "description": "Include detailed evidence rows.",
-      "title": "Include Evidence",
-      "type": "boolean"
-    },
-    "uscc": {
-      "anyOf": [
-        {
-          "maxLength": 18,
-          "minLength": 18,
-          "pattern": "^[0-9A-Z]{18}$",
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "18-character Unified Social Credit Code.",
-      "title": "Uscc"
-    }
-  },
-  "title": "FullEvidenceRequest",
-  "type": "object"
-}
    • addedInput schema / $defs / SupplierIdentity
      Added value: +{
+  "properties": {
+    "company": {
+      "anyOf": [
+        {
+          "maxLength": 200,
+          "minLength": 2,
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Chinese legal company or supplier name.",
+      "title": "Company"
+    },
+    "uscc": {
+      "anyOf": [
+        {
+          "maxLength": 18,
+          "minLength": 18,
+          "pattern": "^[0-9A-Z]{18}$",
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "18-character Unified Social Credit Code.",
+      "title": "Uscc"
+    }
+  },
+  "title": "SupplierIdentity",
+  "type": "object"
+}
    • changedInput schema / properties / request / $ref
      Previous value: -"#/$defs/FullEvidenceRequest"New value: +"#/$defs/SupplierIdentity"
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It clearly discloses that this is a paid operation requiring a USDC wallet, spending authorization, and a specific HTTP header for recovery. It also states limitations: no historical expansion, no automatic paging, and not complete due diligence. This goes beyond what annotations would typically provide.

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 dense but every sentence adds value, covering scope, limitations, setup, and recovery. It front-loads the key information about cost and modules, and includes a link for further guide. No wasted words; it is structured logically for an agent to parse.

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?

Given the complexity of a paid, external API call with recovery options, the description is remarkably complete. It covers prerequisites (x402 client, wallet), input specifics, output scope, and edge-case handling (timeout, recovery). The only minor gap is that it doesn't list the exact nine modules, but the guide link covers that, and the scope is clearly stated.

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 0%, so the description must compensate. It does by specifying that the request should contain an exact Chinese legal name or USCC, which adds meaning beyond the schema's generic field names. The description clarifies the acceptable input format, which is crucial for correct invocation.

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 clearly states the tool's purpose: retrieving nine supplier information modules for a Chinese supplier, with current status and first page of up to 10 records per list. It specifies the resource (Chinese supplier evidence) and the verb (get), distinguishing it from the sibling basic version by emphasizing 'full' and detailing the scope.

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?

Provides explicit guidance: requires a paid USDC payment, a specific authentication method, and the use of exact Chinese legal name or USCC rather than guessed English names. It also mentions the optional recovery process and warns against automatic repayment after timeout, which helps the agent decide when to use this tool and what prerequisites are needed.

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

All CN Evidence toolsInspect
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