longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Shareholders

shareholder

Read-onlyIdempotent

Retrieve institutional shareholders for a given security symbol. Get ownership data to analyze investor positions.

Instructions

Get institutional shareholders for a symbol.

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. "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.

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": {
-    "ShareholderItem": {
-      "properties": {
-        "change": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "change_type": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "institution": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "ratio": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "reported_at": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "shares": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "shareholders": {
-      "items": {
-        "$ref": "#/$defs/ShareholderItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"SymbolParam"
```
Changed11 schema fields changedv0.6.0Jun 26, 2026
- removedOutput schema / $defs / ShareholderItem / description
```
Removed value: -"One holder in `shareholder`'s `shareholders`.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / $defs / ShareholderItem / properties / change / description
```
Removed value: -"Change in shares."
```
- removedOutput schema / $defs / ShareholderItem / properties / change_type / description
```
Removed value: -"Direction / kind of change."
```
- removedOutput schema / $defs / ShareholderItem / properties / institution / description
```
Removed value: -"Institution name."
```
- removedOutput schema / $defs / ShareholderItem / properties / ratio / description
```
Removed value: -"Ownership ratio."
```
- removedOutput schema / $defs / ShareholderItem / properties / reported_at / description
```
Removed value: -"Report date."
```
- removedOutput schema / $defs / ShareholderItem / properties / shares / description
```
Removed value: -"Shares held."
```
- removedOutput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
- removedOutput schema / description
```
Removed value: -"Returned by `shareholder`. Wraps a `shareholders` array.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / properties / shareholders / description
```
Removed value: -"Institutional shareholders."
```
- removedOutput schema / title
```
Removed value: -"ShareholderResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "ShareholderItem": {
+      "description": "One holder in `shareholder`'s `shareholders`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "change": {
+          "description": "Change in shares.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "change_type": {
+          "description": "Direction / kind of change.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "institution": {
+          "description": "Institution name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "ratio": {
+          "description": "Ownership ratio.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "reported_at": {
+          "description": "Report date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "shares": {
+          "description": "Shares held.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `shareholder`. Wraps a `shareholders` array.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "shareholders": {
+      "description": "Institutional shareholders.",
+      "items": {
+        "$ref": "#/$defs/ShareholderItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "ShareholderResponse",
+  "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

B3.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, which fully cover the safety profile. The description adds no behavioral context beyond the bare purpose—no mention of output format, pagination, rate limits, or any special handling. It does not contradict annotations, but it provides zero additional transparency.

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 sentence that is direct and front-loaded. It states the action and resource immediately with no wasted words. It is appropriately concise for such a simple tool.

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 the low complexity (2 params, no nested objects, no output schema), the description is mostly complete. The agent knows what the tool does and has the required parameter from the schema. The only minor gap is that it does not hint at what the response contains (e.g., list of institutions with percentages), but this is not critical for calling the tool correctly.

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?

The schema describes both parameters fully, including the 'symbol' parameter with an example and a warning about canonical form. Schema description coverage is 100%, so the description does not need to add parameter meaning. The phrase 'for a symbol' adds no new information, so a baseline 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 states a clear verb and resource: 'Get institutional shareholders' and specifies the input 'for a symbol.' It is not a tautology and gives the agent a concrete idea of the tool's function. However, it does not explicitly distinguish this from related siblings like 'shareholder_detail' or 'shareholder_top', so it lacks explicit differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention conditions like 'for a quick overview of institutional holders' versus more detailed breakdowns available in sibling tools. There is no mention of why an agent would choose this over related shareholders tools.

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

Deploy Server

Shareholders

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools