Skip to main content
Glama

Hong Kong Company Registry & Due Diligence (86hc.com)

batch_get_company_details

Read-onlyIdempotent

Batch query holographic statutory profiles of 1 to 10 Hong Kong companies simultaneously. Works WITHOUT an API key (3 free companies/day per user/IP; 20 free companies/day with a free API key from https://www.86hc.com/user). Returns Chinese/English legal names, 7-digit CR No., 8-digit Business Registration Number (BRN / Foreign TIN for IRS Form W-8BEN-E) & exemption status, live/dissolved status, incorporation date, annual return date (MM-DD), entity type, governing law (Cap. 622), registered office address, historical former names, and verified ICRIS statutory filings summary with authentic barcodes.

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": {
      "companies": "<companies>"
    },
    "name": "batch_get_company_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoOptional 86hc.com MCP API key (format: hkq_live_xxxx). Omit or leave empty to use the automatic Guest IP Trial Mode (3 free company detail queries/day + direct Stripe filing orders without a key). Free API key with 20 daily company queries available at https://www.86hc.com/user
companiesYesArray of 1 to 10 company identifiers (7-digit CR number, 8-digit BRN, or exact Chinese/English company name).
identifiersNoAlias for companies: array of 1 to 10 company identifiers (CR number, 8-digit BRN, or company name).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Optional 86hc.com MCP API key (format: hkq_live_xxxx). Required only if not already provided via HTTP Header (X-API-Key / Authorization: Bearer) or URL query param (?api_key=...). Free key with 20 daily company queries available at https://www.86hc.com/user"New value: +"Optional 86hc.com MCP API key (format: hkq_live_xxxx). Omit or leave empty to use the automatic Guest IP Trial Mode (3 free company detail queries/day + direct Stripe filing orders without a key). Free API key with 20 daily company queries available at https://www.86hc.com/user"
  2. Changed3 schema fields changed
    • addedInput schema / properties / api_key
      Added value: +{
      +  "description": "Optional 86hc.com MCP API key (format: hkq_live_xxxx). Required only if not already provided via HTTP Header (X-API-Key / Authorization: Bearer) or URL query param (?api_key=...). Free key with 20 daily company queries available at https://www.86hc.com/user",
      +  "type": "string"
      +}
    • changedInput schema / properties / companies / description
      Previous value: -"Array of 1 to 10 identifiers (CR number, 8-digit BRN, or exact company name)."New value: +"Array of 1 to 10 company identifiers (7-digit CR number, 8-digit BRN, or exact Chinese/English company name)."
    • addedInput schema / properties / identifiers
      Added value: +{
      +  "description": "Alias for companies: array of 1 to 10 company identifiers (CR number, 8-digit BRN, or company name).",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, and the description adds real behavior beyond that: dual auth modes, explicit per-day and per-company quotas, and the exact data returned including historical names and ICRIS filings. It stops short of describing partial-batch failure behavior or what happens when an identifier in the array resolves to nothing, which matters for a batch tool.

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 quota terms are front-loaded before the long field enumeration, and every listed field earns its place since no output schema exists. The second sentence is a dense run-on list and the word 'holographic' is unexplained jargon, which costs some readability.

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?

With no output schema, the description correctly carries the burden of describing return values in detail, and it also covers auth, quotas and identifier formats. For a batch read-only query of moderate complexity, nothing essential to correct invocation is missing apart from edge-case error semantics.

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 100%, so all three parameters (api_key, companies, identifiers) are already documented in the schema, including the accepted identifier formats. The description adds almost nothing parameter-specific — notably it never mentions the 'identifiers' alias, so an agent must read the schema to discover the duplicate array. Baseline 3 applies.

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 ('Batch query') plus the exact resource ('holographic statutory profiles of 1 to 10 Hong Kong companies simultaneously') and even enumerates the output fields, so the agent knows precisely what it gets back. It is clearly distinguishable from siblings like get_company_filings or search_companies because it is scoped to batch profile retrieval by identifier.

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 quota and authentication context ('Works WITHOUT an API key; 3 free companies/day... 20 free companies/day with a free API key'), which implicitly tells the agent when this call is viable. However, it never states when to prefer this over sibling tools such as search_companies or get_company_filings, and no exclusions or prerequisites are spelled out.

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.