longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Broker Holding Detail

broker_holding_detail

Read-onlyIdempotent

Get full broker holding details for any HK stock symbol, using CCASS participant disclosure data to show positions and changes.

Instructions

Get full broker holding detail list for a symbol (HK stocks only; sourced from HKEX CCASS participant disclosure).

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": {
      "symbol": "<symbol>"
    },
    "name": "broker_holding_detail"
  }
}

Input Schema

Name	Required	Description	Default
`_jq`	No	Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data \| map({symbol}). Omit for the full response.
`symbol`	Yes	Security symbol, e.g. "700.HK". Use the canonical form — a padded code like "00700.HK" returns an empty record, not an error.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.12.0Sep 23, 2026

addedInput schema / properties / _jq / description

Added value: +"Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response."

changedInput schema / properties / symbol / description

Previous value: -"Security symbol, e.g. \"700.HK\""New value: +"Security symbol, e.g. \"700.HK\". Use the canonical form — a padded code like \"00700.HK\" returns an empty record, not an error."

Changed2 schema fields changedv0.10.6Sep 10, 2026

addedInput schema / properties / _jq
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / (root)

Previous value: -{
-  "$defs": {
-    "BrokerHoldingDetailItem": {
-      "properties": {
-        "broker_id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "broker_name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "holding_change": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "holding_quantity": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "holding_ratio": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "items": {
-      "items": {
-        "$ref": "#/$defs/BrokerHoldingDetailItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"SymbolParam"
```
Changed10 schema fields changedv0.6.0Jun 26, 2026
- removedOutput schema / $defs / BrokerHoldingDetailItem / properties / broker_id / description
```
Removed value: -"Broker (participant) number."
```
- removedOutput schema / $defs / BrokerHoldingDetailItem / properties / broker_name / description
```
Removed value: -"Broker (participant) name."
```
- removedOutput schema / $defs / BrokerHoldingDetailItem / properties / date / description
```
Removed value: -"Disclosure date (yyyy-mm-dd)."
```
- removedOutput schema / $defs / BrokerHoldingDetailItem / properties / holding_change / description
```
Removed value: -"Change in shares held."
```
- removedOutput schema / $defs / BrokerHoldingDetailItem / properties / holding_quantity / description
```
Removed value: -"Shares held by this broker."
```
- removedOutput schema / $defs / BrokerHoldingDetailItem / properties / holding_ratio / description
```
Removed value: -"Holding as a ratio of total issued shares."
```
- removedOutput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
- removedOutput schema / description
```
Removed value: -"Returned by `broker_holding_detail`. Wraps an `items` array of the full\nbroker holding list for an HK stock (HKEX CCASS participant disclosure).\nSubset of the wire response."
```
- removedOutput schema / properties / items / description
```
Removed value: -"Full broker holding detail entries."
```
- removedOutput schema / title
```
Removed value: -"BrokerHoldingDetailResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "BrokerHoldingDetailItem": {
+      "properties": {
+        "broker_id": {
+          "description": "Broker (participant) number.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "broker_name": {
+          "description": "Broker (participant) name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "date": {
+          "description": "Disclosure date (yyyy-mm-dd).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "holding_change": {
+          "description": "Change in shares held.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "holding_quantity": {
+          "description": "Shares held by this broker.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "holding_ratio": {
+          "description": "Holding as a ratio of total issued shares.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `broker_holding_detail`. Wraps an `items` array of the full\nbroker holding list for an HK stock (HKEX CCASS participant disclosure).\nSubset of the wire response.",
+  "properties": {
+    "items": {
+      "description": "Full broker holding detail entries.",
+      "items": {
+        "$ref": "#/$defs/BrokerHoldingDetailItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "BrokerHoldingDetailResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026
Removedv0.4.0May 21, 2026
Addedv0.3.2May 19, 2026
Removedv0.3.1May 15, 2026
First observedv0.1.12May 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already establish that this is read-only, idempotent, and non-destructive, so the bar is lower. The description adds useful context about market scope and data provenance, but it does not describe response format, pagination, or size behavior, which would be needed for a fuller behavioral picture.

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?

One sentence with no filler; the core action, market constraint, and source are all front-loaded. Every element earns its place.

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 simple read-only lookup with one required parameter, the description plus schema is nearly complete: it states the market, source, and what is returned. A mention of response shape or pagination would make it fully complete, but the word 'list' and the robust symbol schema cover most agent needs.

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%, including the canonical symbol format caveat about padded codes, so the schema already handles parameter semantics. The description only repeats 'for a symbol' and adds no extra parameter detail.

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?

The description names a specific verb ('Get') and resource ('full broker holding detail list') and adds concrete scope: HK stocks only and data sourced from HKEX CCASS participant disclosure. It is clear, but it does not explicitly distinguish this from sibling tools such as broker_holding or broker_holding_daily.

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 'HK stocks only' constraint and the HKEX CCASS source give clear context about when the tool applies, and implicitly warn against non-HK symbols. However, it never mentions alternatives or explicitly says when to choose this over sibling holding tools, leaving the routing decision to inference.

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

Deploy Server