Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersScoreDiscussions(1)Admin
Rust
Hybrid

Broker Holding Detail

broker_holding_detail
Read-onlyIdempotent

Retrieve the full broker holding detail list for a Hong Kong stock symbol, sourced from HKEX CCASS participant disclosures, to see how brokers hold shares.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesSecurity symbol, e.g. "700.HK"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  2. Changed10 schema fields changedv0.6.0
    • 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"
  3. Changed1 schema field changedv0.5.6
    • 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"
+}
  4. Addedv0.4.5
  5. Removedv0.4.0
  6. Addedv0.3.2
  7. Removedv0.3.1
  8. First observedv0.1.12

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds context about data source (HKEX CCASS) and market restriction (HK stocks only), which is useful but does not elaborate on the 'detail list' nature or pagination. It provides some value beyond annotations but is not comprehensive.

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 a single concise sentence (15 words) with no extraneous information. It front-loads the key action 'Get full broker holding detail list' and efficiently conveys constraints.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple input (1 param, no enums) and presence of an output schema, the description is adequate but lacks differentiation from sibling tools. It does not explain what makes this 'detail' versus other broker holding tools, which is a gap for an agent deciding between them.

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 coverage is 100% and the parameter 'symbol' has a clear description. The tool description does not add any additional meaning beyond stating it is 'for a symbol', which is already covered by the schema. Baseline score of 3 is appropriate.

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 clearly states it gets a 'full broker holding detail list for a symbol', with specific constraints (HK stocks only, sourced from HKEX CCASS). This distinguishes it from sibling tools like 'broker_holding' and 'broker_holding_daily' by implying a more detailed list, but does not explicitly differentiate.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus its siblings (e.g., 'broker_holding' or 'broker_holding_daily'). There is no mention of prerequisites, limitations, or context for use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/longbridge/longbridge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server