Skip to main content
Glama
longbridge

longbridge

Official

Top 20 Shareholders

shareholder_top
Read-onlyIdempotent

Identify the top 20 major shareholders for any security across reporting periods. Drill into a holder's full trade history to analyze investment behavior.

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
NameRequiredDescriptionDefault
symbolYesSecurity symbol, e.g. "AAPL.US"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
infoNo

Schema Changelog

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

  1. Changed1 schema field changedv0.8.7
    • addedOutput schema / $defs / ShareholderTopHolder / properties / title
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"ShareholderTopParam"
  3. Changed15 schema fields changedv0.6.0
    • 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"
  4. Changed1 schema field changedv0.5.6
    • 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"
      +}
  5. Addedv0.4.5

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the operation as read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond annotations: the result is limited to Top 20 holders, spans reporting periods, and outputs an object_id usable with shareholder_detail. No contradiction with annotations.

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 short sentences deliver the core purpose and the key drill-down workflow. No filler or redundancy exists, and the most important information is front-loaded.

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

Completeness5/5

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

For a single-parameter, output-schema-backed read-only tool, the description is sufficient: it defines scope, data categories, reporting-period behavior, and the related drill-down path. The presence of an output schema and strong annotations further reduces the need for extra explanatory text.

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 fully documents the single 'symbol' parameter with an example, so the description does not need to repeat that. The mention of 'object_id' is not a schema parameter but is useful context about the returned data, and it adds a small amount of semantic value beyond the schema.

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?

The description starts with a specific action and resource: 'Get Top 20 major shareholders', with clear categories (institutions, individuals, insiders) and reporting-period coverage. It distinguishes itself from the sibling 'shareholder_detail' by framing the top-level view and pointing to the drill-down tool.

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

Usage Guidelines4/5

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

The description clearly implies when to use this tool: to retrieve the top-20 shareholder list across reporting periods. It also provides composability guidance by referencing 'object_id with shareholder_detail' for deeper holder history, although it does not exhaustively compare against every sibling tool.

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