longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Broker Holding (Daily)

broker_holding_daily

Read-onlyIdempotent

Retrieve daily holding history for a broker in an HK stock using broker participant ID, sourced from HKEX CCASS disclosures.

Instructions

Get daily holding history for a specific broker (by broker_id) in a symbol (HK stocks only; sourced from HKEX CCASS participant disclosure).

Input Schema

TableJSON Schema

Name	Required	Description
`_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.
`broker_id`	Yes	Broker participant number

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": {
-    "BrokerHoldingDailyItem": {
-      "properties": {
-        "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/BrokerHoldingDailyItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"BrokerHoldingDailyParam"
```
Changed8 schema fields changedv0.6.0Jun 26, 2026
- removedOutput schema / $defs / BrokerHoldingDailyItem / properties / date / description
```
Removed value: -"Disclosure date (yyyy-mm-dd)."
```
- removedOutput schema / $defs / BrokerHoldingDailyItem / properties / holding_change / description
```
Removed value: -"Change in shares held versus the prior day."
```
- removedOutput schema / $defs / BrokerHoldingDailyItem / properties / holding_quantity / description
```
Removed value: -"Shares held by this broker on that date."
```
- removedOutput schema / $defs / BrokerHoldingDailyItem / 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_daily`. Wraps an `items` array of the daily\nholding history for one broker in an HK stock. Subset of the wire response."
```
- removedOutput schema / properties / items / description
```
Removed value: -"Daily holding history entries."
```
- removedOutput schema / title
```
Removed value: -"BrokerHoldingDailyResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "BrokerHoldingDailyItem": {
+      "properties": {
+        "date": {
+          "description": "Disclosure date (yyyy-mm-dd).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "holding_change": {
+          "description": "Change in shares held versus the prior day.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "holding_quantity": {
+          "description": "Shares held by this broker on that date.",
+          "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_daily`. Wraps an `items` array of the daily\nholding history for one broker in an HK stock. Subset of the wire response.",
+  "properties": {
+    "items": {
+      "description": "Daily holding history entries.",
+      "items": {
+        "$ref": "#/$defs/BrokerHoldingDailyItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "BrokerHoldingDailyResponse",
+  "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

A4.2/5.0

Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is established. The description adds useful behavioral context beyond annotations: the data is sourced from HKEX CCASS and limited to HK stocks, and the tool returns daily history rather than current holdings. No contradictions.

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 tightly written sentence that front-loads the core operation and immediately adds the important scoping constraints (broker, symbol, HK-only, data source). Every word earns its place with no 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 a read-only, two-required-parameter query tool, the description plus the rich parameter schema gives an agent enough to invoke it correctly. There is no output schema, but the return concept ('daily holding history') is clear from the name and description. Date-range or pagination details would strengthen it but are not essential for a first correct call.

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%, and the schema already documents both required parameters, including canonical symbol format and empty-record behavior. The description merely repeats symbol and broker_id in prose without adding new parameter-level meaning, so the baseline 3 is appropriate.

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?

The description states a specific verb ('Get'), a specific resource ('daily holding history for a specific broker ... in a symbol'), and scoping constraints ('HK stocks only', 'HKEX CCASS participant disclosure'). This clearly differentiates it from sibling tools like broker_holding or broker_holding_detail through the 'daily' qualifier.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The context is clear: use this tool when you need historical daily broker holding data for a specific symbol and broker. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5, but the intended usage is unambiguous.

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

Deploy Server

Broker Holding (Daily)

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools