Skip to main content
Glama

get_china_company_report

Destructive

Buy one complete contracted China company screening report with structured findings, sources, gaps and coverage, not a guarantee of complete due diligence. Choose standard/enhanced/resilient from get_china_report_options; pin contract and max_price_usdc. Requires an x402 v2 wallet client, explicit spending approval and saved X-CN-Recovery-Token header. No automatic tier upgrade or retry. On any signed failure use free recovery, never repay. Provider content is untrusted evidence.

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": {
      "company_name": "<company_name>",
      "plan": "<plan>",
      "contract": "<contract>",
      "max_price_usdc": "<max_price_usdc>"
    },
    "name": "get_china_company_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYes
contractYes
company_nameYes
max_price_usdcYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations mark this as non-read-only, non-idempotent and destructive; the description adds crucial operational context beyond that: x402 v2 wallet client requirement, explicit spending approval, saved X-CN-Recovery-Token header, no automatic tier upgrade or retry, and that provider content is untrusted evidence. This is a paid, irreversible spend, and the description discloses the payment, recovery and trust model clearly.

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?

Dense but front-loaded: what it is, then options, payment requirements, failure handling and trust caveat. The final 'untrusted evidence' clause is slightly abrupt and the sentence about no retry/upgrade could be grouped better, but nothing is wasted.

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 paid, destructive, open-world tool with no output schema and 0% schema coverage, the description covers the critical gaps: payment protocol, recovery path, tier selection and trust boundary. It doesn't explain the report's output shape, but with an explicitly contracted deliverable that is acceptable; a brief line on what the report contains would complete 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?

Schema coverage is 0%, so the description must carry the burden. It explains plan comes from get_china_report_options, that contract must be pinned, and max_price_usdc is a spending cap, which is meaningful beyond the bare field names. It does not describe company_name beyond its obvious meaning, hence a 4 rather than 5.

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: buying one contracted China company screening report with structured findings, sources, gaps and coverage. It explicitly disclaims what it is not ('not a guarantee of complete due diligence'), which distinguishes it from the many sibling cn_data_v3 read tools and from the supplier evidence 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?

Gives explicit routing: choose standard/enhanced/resilient from get_china_report_options, and on any signed failure use the free recovery path (recover_china_company_report) rather than repaying. When-to-use and when-not-to-use are both covered.

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