Skip to main content
Glama
Sign In

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

by com.86hc
OverviewDiscussionsAdmin

create_filing_order

Create a paid filing retrieval order for an official Hong Kong Companies Registry statutory document (ONLY call this when the user explicitly wants to purchase/retrieve an official PDF document). Works directly WITHOUT an API key! Returns both web_cashier_url (86hc.com 3-in-1 Web Cashier supporting Mainland Alipay 支付宝, AlipayHK 香港支付宝, and Stripe / Apple Pay) and checkout_url (direct Stripe / Alipay checkout link). Pass either an authentic ICRIS barcode OR pass identifier + doc_code (e.g. NAR1, NNC1, A&A) and the server will automatically select the latest verified ICRIS barcode. Upon payment completion, the user receives the official PDF download link and earns +10 bonus permanent company query credits.

Input Schema

NameRequiredDescriptionDefault
emailNoOptional user email address to receive the official PDF download link.
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
barcodeNoAuthentic ICRIS document barcode obtained from get_company_filings or batch_get_company_details. If omitted, provide identifier + doc_code to auto-select the latest verified barcode.
doc_codeNoStatutory form code (e.g. NAR1, NNC1, ND2A, A&A). Defaults to NAR1.
doc_nameNoDocument title or form code (e.g. NAR1 Annual Return).
identifierNoCompany CR number, 8-digit BRN, or company name.
pay_methodNoPreferred payment method: alipay (Mainland Alipay 支付宝), alipay_hk (AlipayHK 香港支付宝), or stripe (Visa / MasterCard / Apple Pay). Note: web_cashier_url always allows switching among all 3 methods.stripe
company_nameNoName or CR number of the company.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / pay_method
      Added value: +{
+  "default": "stripe",
+  "description": "Preferred payment method: alipay (Mainland Alipay 支付宝), alipay_hk (AlipayHK 香港支付宝), or stripe (Visa / MasterCard / Apple Pay). Note: web_cashier_url always allows switching among all 3 methods.",
+  "enum": [
+    "alipay",
+    "alipay_hk",
+    "stripe"
+  ],
+  "type": "string"
+}
  2. Changed4 schema fields 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"
    • changedInput schema / properties / barcode / description
      Previous value: -"Authentic ICRIS document barcode obtained from get_company_filings or batch_get_company_details."New value: +"Authentic ICRIS document barcode obtained from get_company_filings or batch_get_company_details. If omitted, provide identifier + doc_code to auto-select the latest verified barcode."
    • changedInput schema / properties / doc_code / description
      Previous value: -"Statutory form code (e.g. NAR1, NNC1, ND2A, A&A)."New value: +"Statutory form code (e.g. NAR1, NNC1, ND2A, A&A). Defaults to NAR1."
    • removedInput schema / required
      Removed value: -[
-  "barcode"
-]
  3. Changed5 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 / barcode / description
      Previous value: -"Authentic document barcode obtained from get_company_filings."New value: +"Authentic ICRIS document barcode obtained from get_company_filings or batch_get_company_details."
    • addedInput schema / properties / doc_code
      Added value: +{
+  "description": "Statutory form code (e.g. NAR1, NNC1, ND2A, A&A).",
+  "type": "string"
+}
    • changedInput schema / properties / email / description
      Previous value: -"User email address to receive download link."New value: +"Optional user email address to receive the official PDF download link."
    • addedInput schema / properties / identifier
      Added value: +{
+  "description": "Company CR number, 8-digit BRN, or company name.",
+  "type": "string"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / company_name / description
      Previous value: -"Name of the company."New value: +"Name or CR number of the company."
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false) by disclosing that no API key is required, that a Guest IP Trial Mode exists, that two checkout URLs are returned with their payment-method coverage, and what happens post-payment (PDF link delivered, +10 credits earned). This is real behavioral context for a paid mutation tool, not a restatement of the hints.

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?

The core purpose and the ONLY-call constraint are front-loaded in the first sentence, which is correct. There is some promotional padding ('Works directly WITHOUT an API key!', the 86hc.com brand and '+10 bonus permanent company query credits') and the third sentence is dense, but the information is substantive rather than filler.

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 an 8-parameter, no-output-schema payment tool, the description covers the return payload (web_cashier_url and checkout_url plus their payment coverage) and the post-payment outcome. It stops short of stating URL expiry or what an agent should do if order creation fails, which are the remaining operational gaps.

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 100%, so the baseline is 3, but the description adds genuinely useful semantics on top: it explains the either/or logic between barcode and identifier+doc_code, and that the server auto-selects the latest verified ICRIS barcode when the latter pair is supplied. It does not clarify the doc_name vs doc_code overlap, which is the one ambiguity left.

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: 'Create a paid filing retrieval order for an official Hong Kong Companies Registry statutory document.' This is clearly distinguishable from read-only siblings like get_company_filings and from check_filing_order_status, since it names the purchase/retrieval-order action explicitly.

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?

Contains an explicit gating condition in caps: 'ONLY call this when the user explicitly wants to purchase/retrieve an official PDF document.' It also routes the agent to the correct upstream tools for input sourcing ('barcode obtained from get_company_filings or batch_get_company_details'), so both when-to-use and where-to-get-inputs are covered.

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

All Hong Kong Company Registry & Due Diligence (86hc.com) 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