Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersScoreDiscussions(1)Admin
Rust
Hybrid

Broker Holding (Daily)

broker_holding_daily
Read-onlyIdempotent

Get daily holding history for a broker in an HK stock by broker ID and symbol, based on HKEX CCASS data. Monitor broker position changes over time.

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
NameRequiredDescriptionDefault
symbolYesSecurity symbol, e.g. "700.HK"
broker_idYesBroker participant number

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: -"BrokerHoldingDailyParam"
  2. Changed8 schema fields changedv0.6.0
    • 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"
  3. Changed1 schema field changedv0.5.6
    • 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"
+}
  4. Addedv0.4.5
  5. Removedv0.4.0
  6. Addedv0.3.2
  7. Removedv0.3.1
  8. First observedv0.1.12

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare safety and idempotency. Description adds context about data source and daily frequency, but does not disclose additional behavioral traits like rate limits or pagination. Baseline 3 since annotations cover core safety profile.

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?

Single sentence, front-loaded with action and scope. No superfluous words. Efficient and clear.

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?

Given output schema exists to document return values, and annotations cover safety, the description is adequate. It specifies source and scope, though date range or history depth is missing. Still fairly complete for a data retrieval tool.

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 both parameters are already documented. Description restates purpose but does not add new meaning beyond schema (e.g., format or constraints). Baseline 3.

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?

Clearly states it retrieves daily holding history for a specific broker and symbol, with explicit scope (HK stocks) and data source (HKEX CCASS). Distinguishes from siblings like broker_holding and broker_holding_detail.

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?

Implied usage for HK stocks only, but no explicit guidance on when to use this tool vs. alternatives (e.g., broker_holding, broker_holding_detail). No when-not or exclusion criteria provided.

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