shareholderGet institutional holders for a security symbol to identify major investors and ownership structure.
Get institutional shareholders for a symbol.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Security symbol, e.g. "700.HK" |
| Name | Required | Description | Default |
|---|---|---|---|
| shareholders | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.7.1Input schema / titleRemoved value: -"SymbolParam"v0.6.0Output schema / $defs / ShareholderItem / descriptionRemoved value: -"One holder in `shareholder`'s `shareholders`.\n\nSubset of documented fields; upstream may return more."Output schema / $defs / ShareholderItem / properties / change / descriptionRemoved value: -"Change in shares."Output schema / $defs / ShareholderItem / properties / change_type / descriptionRemoved value: -"Direction / kind of change."Output schema / $defs / ShareholderItem / properties / institution / descriptionRemoved value: -"Institution name."Output schema / $defs / ShareholderItem / properties / ratio / descriptionRemoved value: -"Ownership ratio."Output schema / $defs / ShareholderItem / properties / reported_at / descriptionRemoved value: -"Report date."Output schema / $defs / ShareholderItem / properties / shares / descriptionRemoved value: -"Shares held."Output schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Output schema / descriptionRemoved value: -"Returned by `shareholder`. Wraps a `shareholders` array.\n\nSubset of documented fields; upstream may return more."Output schema / properties / shareholders / descriptionRemoved value: -"Institutional shareholders."Output schema / titleRemoved value: -"ShareholderResponse"v0.5.6Output 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"
+}v0.4.5v0.4.0v0.3.2v0.3.1v0.1.12Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the agent knows this is a safe read-only operation. The description adds minimal behavioral context beyond the resource type ('institutional shareholders'). No mention of output structure or pagination, but the safety profile is covered by annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with no wasted words. It conveys the essential purpose without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is minimal but acceptable given the tool's simplicity (one parameter, output schema present). However, it could provide more context about the output (e.g., data fields) or usage hints, especially compared to siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 100% schema description coverage, the input schema already documents the single parameter 'symbol' with an example. The description merely restates 'for a symbol', adding no new semantic value beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Get institutional shareholders for a symbol', providing a specific verb and resource. However, it does not explicitly differentiate from sibling tools like 'shareholder_detail' or 'fund_holder', which may also retrieve shareholder data for a symbol.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description offers no guidance on when to use this tool versus alternatives such as 'shareholder_top' or 'institutional_views'. Given the large set of sibling tools, this omission makes it harder for the agent to select the correct tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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