Skip to main content
Glama

Holdings of an investor, fund or person

get_holders
Read-only

Returns what one investor, fund or person holds in the tracked companies, from SEC filings (13F, Schedule 13D/G, Forms 3, 4 and 5). With holder (a key, a name such as 'Vanguard' or 'Jensen Huang', or the holder value another tool returned): positions with their move and heldSince, sectors, flows, 13D/G declarations, history since 2019, the performance of its declared picks, and for a person each stake broken down. Without holder, a ranked list. Use it when the user asks what a fund, an investor or a person owns, or who bought, sold or performed most. A person has two true figures for one company: shares held (Form 4) and beneficial ownership (13D/G): say which one you quote.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNoWithout `holder`: 'largest' (default), 'investors' (universe companies filing 13F), 'buyers' or 'sellers' (by net move), 'declarants' (Schedule 13D/G holders filing no 13F), 'individuals' (people, from their 13D/G), 'performance' (active managers ranked by the return of their declared AI-stock portfolio).
limitNoRows to return (default 25, max 100): ranked holders, or one holder's positions, `positionsTotal` and `positionsTruncated` say how many it has.
orderNoWith list 'performance': 'best' (default: highest return first) or 'worst' (lowest first).
holderNoFor one holder's detail: its key from a list (vanguard, blackrock, nvidia), a name ('BlackRock', 'Vanguard', or a person's name), or the `holder` value another tool returned (for a director, their name and a ticker, e.g. 'Larry Ellison (ORCL)').
periodNoWith list 'performance': 'quarter' (default: the last completed quarter), 'year', '3y' or '5y', quarterly returns chained.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Rows to return (default 25, max 100): ranked holders, or one holder's positions — `positionsTotal` and `positionsTruncated` say how many it has."New value: +"Rows to return (default 25, max 100): ranked holders, or one holder's positions, `positionsTotal` and `positionsTruncated` say how many it has."
    • changedInput schema / properties / period / description
      Previous value: -"With list 'performance': 'quarter' (default: the last completed quarter), 'year', '3y' or '5y' — quarterly returns chained."New value: +"With list 'performance': 'quarter' (default: the last completed quarter), 'year', '3y' or '5y', quarterly returns chained."
  2. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Rows to return (default 25, max 100)."New value: +"Rows to return (default 25, max 100): ranked holders, or one holder's positions — `positionsTotal` and `positionsTruncated` say how many it has."
  3. Changed2 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
  4. Changed2 schema fields changed
    • changedInput schema / properties / holder / description
      Previous value: -"For one holder's detail: its key from a list (vanguard, blackrock, nvidia, elon-r-musk), a name ('BlackRock', 'Elon Musk', 'Jensen Huang') or a director's SEC CIK (as get_ownership returns it)."New value: +"For one holder's detail: its key from a list (vanguard, blackrock, nvidia), a name ('BlackRock', 'Vanguard', or a person's name), or the `holder` value another tool returned (for a director, their name and a ticker, e.g. 'Larry Ellison (ORCL)')."
    • changedInput schema / properties / order / description
      Previous value: -"With list 'performance': 'best' (default) or 'worst'."New value: +"With list 'performance': 'best' (default: highest return first) or 'worst' (lowest first)."
  5. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/destructive annotations it discloses data lineage, the history horizon (since 2019), truncation behavior via `positionsTotal`/`positionsTruncated`, and a genuinely important ambiguity warning: a person has two distinct true figures (Form 4 shares vs. 13D/G beneficial ownership) and the agent must state which it quotes. That is substantive behavioral guidance an agent could not infer from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and mode split are front-loaded, and the parenthetical return-content inventory earns its place since there is no output schema. It is dense but not padded; the persona examples ('Vanguard', 'Jensen Huang') add lookup value rather than noise.

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?

All five parameters are documented in-schema and reinforced in prose, both modes are covered, and with no output schema the description compensates by enumerating what the response contains. Nothing essential for a correct first call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real semantics on top: what `holder` accepts (key, name, or a `holder` string returned by another tool, e.g. 'Larry Ellison (ORCL)') and how omitting it flips behavior to list mode. It reinforces rather than duplicates the enum documentation.

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?

Opens with a specific verb and resource ('Returns what one investor, fund or person holds') plus the data provenance (13F, 13D/G, Forms 3/4/5), and it explicitly defines the two operating modes (with vs. without `holder`). It does not distinguish itself from close siblings like get_ownership, get_insider_trading or get_fund_flows, which an agent must disambiguate on its own.

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?

Gives a concrete trigger ('Use it when the user asks what a fund, an investor or a person owns, or who bought, sold or performed most') and explains the mode split: detail when `holder` is supplied, ranked list otherwise. It also notes accepting a `holder` value from another tool, which supports chaining. No explicit exclusions against sibling tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.