Skip to main content
Glama

cn_data_v3_company_detail

Company registration and legal identity. Exact Chinese legal name or Jinghai company ID; no fuzzy match or direct USCC lookup. 0.011000 USDC per single call. Pass arguments matching get_cn_data_tool_schema("v3_company_detail"). One selected Chinese company data tool call. Additional pages require separate requests. No completeness or safety guarantee.

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": {
      "arguments": "<arguments>"
    },
    "name": "cn_data_v3_company_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and delivers real value: per-call pricing (0.011 USDC), the fact that additional pages require separate requests, and an explicit 'No completeness or safety guarantee' disclaimer. It omits auth/permission context, keeping it short of a 5.

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?

Purpose and identifier constraints are front-loaded, and the pricing/pagination/disclaimer sentences each earn their place. The line 'One selected Chinese company data tool call.' is near-redundant and the telegraphic style makes the flow choppy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must convey what comes back; 'Company registration and legal identity' is a vague content hint and no return fields or structure are described. Cost, pagination, and the quality caveat are covered well, but the payload shape is left to inference.

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 0% and the lone 'arguments' object is a passthrough with no documented properties, so the description must compensate. It does add the accepted identifier types (exact Chinese legal name or Jinghai company ID) and points at get_cn_data_tool_schema('v3_company_detail'), but it never enumerates the actual argument keys, leaving the agent one indirection away from the real contract.

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?

States a concrete verb/resource pair ('Company registration and legal identity') that is distinguishable from the many sibling list/count tools by naming the core entity-detail resource. It does not explicitly contrast with near-neighbors like cn_data_v3_register_header or cn_data_v3_listed_company, so it falls short of a 5.

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 gives input constraints ('Exact Chinese legal name or Jinghai company ID; no fuzzy match or direct USCC lookup'), which implicitly steer the agent toward name-resolution tooling, but it never names an alternative such as resolve_china_company. Usage context is implied rather than explicit.

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