Skip to main content
Glama

Shareholders of a company

get_ownership
Read-only

Returns one company's shareholders from SEC filings: 13F managers, holders above 5% (Schedule 13D/G), directors, officers and 10% owners (Forms 3, 4 and 5): each with shares, share of the company, date and filing; with the quarter's declared moves (moves), the funds that report the shares (N-PORT) and the 13F history since 2019. Use it when the user asks who owns a company, its largest shareholders, or who bought or sold its shares. Report declaredOwnership as the range it gives, never one number; howToRead explains each figure, and each holder's holder value works in get_holders. A pre-IPO company (e.g. 'anthropic') returns its prospectus's stockholders.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_ownership"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHolders to return (default 20, max 60).
movesNoDeclared moves: 'summary' (default: the quarter's counts, largest sales and buys, every Schedule 13D/G move of the period, insiders), or a full list of the quarter's 13F moves, largest first: 'sales' (reductions and exits), 'exits', 'buys' (new holders and increases), 'all'.
symbolYesTicker or company name, e.g. NVDA, AMD, ASML, 'nvidia', 'taiwan semiconductor'. Case-insensitive.
movesLimitNoMoves to list when `moves` is not 'summary' (default 50, max 500).
movesOffsetNoSkip this many moves (pagination: the previous answer's `next`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +60
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / movesLimit / maximum
      Added value: +500
    • addedInput schema / properties / movesLimit / minimum
      Added value: +1
    • addedInput schema / properties / movesOffset / maximum
      Added value: +100000
    • addedInput schema / properties / movesOffset / minimum
      Added value: +0
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive/closed-world, and the description still adds substantial behavioral context: the underlying filing sources, the instruction to report `declaredOwnership` as a range rather than a single number, the `howToRead` explainer, and the pre-IPO prospectus fallback. That is exactly the kind of interpretation guidance annotations cannot carry.

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?

Front-loaded with what is returned before the usage and caveat sentences. It is a dense single paragraph, but nearly every clause adds information; the `howToRead`/`holder` sentence is the only part that feels like output contract rather than selection guidance.

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?

There is no output schema, so the description carries the return-shape burden and does: it names key response fields (`declaredOwnership`, `howToRead`, `holder`, `next`), explains their interpretation, and covers the pre-IPO edge case. An agent has enough to call it and to report results 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?

Schema description coverage is 100%, with the `moves` enum and pagination semantics (`movesOffset` = previous answer's `next`) already documented in the schema. The description restates that `moves` is the quarter's declared moves but adds no syntax, defaults, or edge-case guidance beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Returns one company's shareholders from SEC filings') and enumerates the exact data sources covered (13F, 13D/G, Forms 3/4/5, N-PORT) plus the quarter's moves. This is clearly differentiated from neighbors like get_holders and get_insider_trading, and even calls out the pre-IPO prospectus case.

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?

Explicit use context is given: 'Use it when the user asks who owns a company, its largest shareholders, or who bought or sold its shares.' It also names get_holders as a downstream tool for a returned value. However, it never says when NOT to use it or why to prefer a sibling (get_holders, get_insider_trading, get_fund_flows) for narrower questions.

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.