Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Broker Holding

broker_holding
Read-onlyIdempotent

Retrieve top broker holding data for Hong Kong stocks from HKEX CCASS disclosures. Identify key participants and their share positions for a symbol.

Instructions

Get top broker holding data for a symbol (HK stocks only; sourced from HKEX CCASS participant disclosure).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_jqNoOptional 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.
periodNoPeriod: "rct_1" (1 day, default), "rct_5" (5 days), "rct_20" (20 days), "rct_60" (60 days)
symbolYesSecurity 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.

  1. Changed2 schema fields changedv0.12.0
    • 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."
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "BrokerHoldingItem": {
-      "properties": {
-        "broker_name": {
-          "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/BrokerHoldingItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"BrokerHoldingParam"
  4. Changed8 schema fields changedv0.6.0
    • removedOutput schema / $defs / BrokerHoldingItem / properties / broker_name / description
      Removed value: -"Broker (participant) name."
    • removedOutput schema / $defs / BrokerHoldingItem / properties / holding_change / description
      Removed value: -"Change in shares held over the period."
    • removedOutput schema / $defs / BrokerHoldingItem / properties / holding_quantity / description
      Removed value: -"Shares held by this broker."
    • removedOutput schema / $defs / BrokerHoldingItem / 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`. Wraps an `items` array of top broker holdings\nfor an HK stock (HKEX CCASS participant disclosure). Subset of the wire\nresponse."
    • removedOutput schema / properties / items / description
      Removed value: -"Top broker holding entries for the requested period."
    • removedOutput schema / title
      Removed value: -"BrokerHoldingResponse"
  5. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "BrokerHoldingItem": {
+      "properties": {
+        "broker_name": {
+          "description": "Broker (participant) name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "holding_change": {
+          "description": "Change in shares held over the period.",
+          "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`. Wraps an `items` array of top broker holdings\nfor an HK stock (HKEX CCASS participant disclosure). Subset of the wire\nresponse.",
+  "properties": {
+    "items": {
+      "description": "Top broker holding entries for the requested period.",
+      "items": {
+        "$ref": "#/$defs/BrokerHoldingItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "BrokerHoldingResponse",
+  "type": "object"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. First observedv0.1.12

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the description does not need to re-state safety. It adds value by disclosing the data source and market scope, but it does not describe pagination, result ranking, or any other runtime behavior.

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?

The description is one efficient sentence with the core verb/resource first, followed by the two most important qualifiers (market scope and data source). No wasted words.

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 data lookup, the description plus a fully documented input schema is sufficient for an agent to select and invoke the tool. It does not define what 'top' means or describe the output shape, but given the simple query nature and strong annotations, this is a minor gap.

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 the parameters are already well documented. The description reinforces the symbol-centric purpose but adds no new semantic detail about period or the jq filter beyond the schema.

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 names a specific action and resource: 'Get top broker holding data for a symbol.' It further narrows scope with 'HK stocks only' and 'sourced from HKEX CCASS participant disclosure,' which distinguishes it from sibling tools like broker_holding_daily, broker_holding_detail, and participants.

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?

It gives a clear applicability boundary ('HK stocks only') and a data-source context, so an agent knows when this tool is relevant. It stops short of explicitly naming alternatives or saying when NOT to use it, which would be necessary for a 5.

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

Deploy Server

Other Tools