longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Top 20 Shareholders

shareholder_top

Read-onlyIdempotent

Retrieve the top 20 major shareholders for a security across reporting periods, covering institutions, individuals, and insiders. Drill into any holder's full trade history.

Instructions

Get Top 20 major shareholders (institutions, individuals, insiders) across reporting periods. Use object_id with shareholder_detail to drill into a holder's full trade history.

Input Schema

TableJSON 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. "AAPL.US"

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field 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."

Changed2 schema fields changedv0.10.6Sep 10, 2026

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

changedOutput schema / (root)

Previous value: -{
-  "$defs": {
-    "ShareholderTopHolder": {
-      "properties": {
-        "filing_date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "object_id": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "percent_shares_held": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "shares_changed": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "shares_held": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "title": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "ShareholderTopPeriod": {
-      "properties": {
-        "period": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "share_holders": {
-          "items": {
-            "$ref": "#/$defs/ShareholderTopHolder"
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "info": {
-      "items": {
-        "$ref": "#/$defs/ShareholderTopPeriod"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.8.7Aug 19, 2026
- addedOutput schema / $defs / ShareholderTopHolder / properties / title
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"ShareholderTopParam"
```
Changed15 schema fields changedv0.6.0Jun 26, 2026
- removedOutput schema / $defs / ShareholderTopHolder / description
```
Removed value: -"One holder in `shareholder_top`'s `share_holders`.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / $defs / ShareholderTopHolder / properties / filing_date / description
```
Removed value: -"Filing date."
```
- removedOutput schema / $defs / ShareholderTopHolder / properties / name / description
```
Removed value: -"Holder name."
```
- removedOutput schema / $defs / ShareholderTopHolder / properties / object_id / description
```
Removed value: -"Holder object id. Pass to `shareholder_detail`."
```
- removedOutput schema / $defs / ShareholderTopHolder / properties / percent_shares_held / description
```
Removed value: -"Percentage of shares held."
```
- removedOutput schema / $defs / ShareholderTopHolder / properties / shares_changed / description
```
Removed value: -"Change in shares held."
```
- removedOutput schema / $defs / ShareholderTopHolder / properties / shares_held / description
```
Removed value: -"Shares held."
```
- removedOutput schema / $defs / ShareholderTopHolder / properties / title
```
Removed value: -{
-  "description": "Holder title / role.",
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
- removedOutput schema / $defs / ShareholderTopPeriod / description
```
Removed value: -"One period snapshot in `shareholder_top`'s `info`.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / $defs / ShareholderTopPeriod / properties / period / description
```
Removed value: -"Reporting period."
```
- removedOutput schema / $defs / ShareholderTopPeriod / properties / share_holders / description
```
Removed value: -"Holders for this period."
```
- removedOutput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
- removedOutput schema / description
```
Removed value: -"Returned by `shareholder_top`. Wraps an `info` array of per-period\nsnapshots, each with a `share_holders` list.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / properties / info / description
```
Removed value: -"Per-period holder snapshots."
```
- removedOutput schema / title
```
Removed value: -"ShareholderTopResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "ShareholderTopHolder": {
+      "description": "One holder in `shareholder_top`'s `share_holders`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "filing_date": {
+          "description": "Filing date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Holder name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "object_id": {
+          "description": "Holder object id. Pass to `shareholder_detail`.",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "percent_shares_held": {
+          "description": "Percentage of shares held.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "shares_changed": {
+          "description": "Change in shares held.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "shares_held": {
+          "description": "Shares held.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "title": {
+          "description": "Holder title / role.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "ShareholderTopPeriod": {
+      "description": "One period snapshot in `shareholder_top`'s `info`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "period": {
+          "description": "Reporting period.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "share_holders": {
+          "description": "Holders for this period.",
+          "items": {
+            "$ref": "#/$defs/ShareholderTopHolder"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `shareholder_top`. Wraps an `info` array of per-period\nsnapshots, each with a `share_holders` list.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "info": {
+      "description": "Per-period holder snapshots.",
+      "items": {
+        "$ref": "#/$defs/ShareholderTopPeriod"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "ShareholderTopResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and side effects. The description adds the data-scope detail 'across reporting periods,' which is a behavioral trait about output coverage, but it does not disclose response format, pagination, or any limits beyond the 'Top 20' fixed count. Given annotations carry the main behavioral burden, the description adds modest extra context.

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?

Two sentences with zero fluff. The purpose is front-loaded, and the second sentence adds a useful cross-reference to a sibling tool. Every word earns its place; it is efficient and well-structured.

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?

For a simple read-only query with two parameters and no output schema, the description explains the core function but leaves some ambiguity about the response structure (e.g., whether it returns data for multiple reporting periods and how those are formatted). Since there is no output schema, the description should carry more of the return-format burden; it doesn't fully do so. Still, the tool is simple enough that the description is minimally adequate.

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% (both symbol and _jq are documented). The description adds no new parameter meaning beyond the schema; it references 'object_id' but that is a parameter of shareholder_detail, not of this tool. Baseline 3 is appropriate since the schema already fully documents the parameters.

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 states a specific verb (Get), resource (Top 20 major shareholders), and scope (institutions, individuals, insiders, across reporting periods). It clearly conveys a top-20 limited list, distinguishing it from a general shareholder list. However, it does not explicitly contrast with the sibling 'shareholder' tool, so the differentiation is implied rather than named.

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?

It provides one usage pointer: 'Use object_id with shareholder_detail to drill into a holder's full trade history,' which tells the agent when to switch to a different tool. But it does not mention when to prefer this over the 'shareholder' sibling or other holder-related tools (e.g., fund_holder, broker_holding). The guidance is partial, not a full when/when-not.

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

Deploy Server

Top 20 Shareholders

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools