Skip to main content
Glama

Insider Ownership Summary

GetInsiderOwnership
Read-only

Get a summary of insider ownership for a stock, ranked by total shares held. Shares come from each insider's most recent SEC Form 3/4/5 filing: the filing's closing balance per security, held directly or through each indirect vehicle the filing names (a trust, partnership or LLC, told apart by its stated nature of ownership and by which balance each trade continues), actual shares only (options and other derivative holdings are excluded), summed into Direct and Indirect columns and restated onto today's split basis, so they can differ from the raw figures in older filings. A vehicle the newest filing does not list is not counted. Last Transaction is the newest trade that filing reports, or Holding when it reports positions only. Former insiders may linger with stale dates or zero shares. Returns at most maxResults insiders (default 30). Use this to understand the insider ownership structure of a company; use GetInsiderTransactions for the underlying trades.

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": {
      "ticker": "<ticker>"
    },
    "name": "GetInsiderOwnership"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNoNumber of ranked insiders to skip before returning rows (default: 0, clamped to 0-100000). For the next page, add the returned row count to the clamped current offset; if the next offset exceeds 100000, narrow the filters instead. Stop when fewer than the effective page size (maxResults clamped to 1-500) are returned, or the response's total has been reached.
tickerYesCompany ticker symbol (e.g., AAPL, MSFT)
maxResultsNoMaximum number of insiders to return (default: 30, max: 500; values outside 1-500 are clamped)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / offset / description
      Previous value: -"Number of ranked insiders to skip before returning rows — pass the previous call's shown count to page past the maxResults cap (default: 0)"New value: +"Number of ranked insiders to skip before returning rows (default: 0, clamped to 0-100000). For the next page, add the returned row count to the clamped current offset; if the next offset exceeds 100000, narrow the filters instead. Stop when fewer than the effective page size (maxResults clamped to 1-500) are returned, or the response's total has been reached."
  2. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Number of ranked insiders to skip before returning rows — pass the previous call's shown count to page past the maxResults cap (default: 0)",
      +  "type": "integer"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, and the description adds substantial context beyond them: it discloses the derivation methodology (Form 3/4/5 closing balances, direct vs. indirect vehicles), exclusions (derivatives and options), restatement onto today's split basis so values can differ from raw filings, the rule that vehicles absent from the newest filing are dropped, and the maxResults default of 30. This is exactly the kind of caveat an agent needs to interpret results correctly.

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

Conciseness3/5

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

The core purpose and the sibling routing are front-loaded, which is good, but the middle is a single sprawling sentence with deeply nested parentheticals about vehicle disambiguation that is hard to parse on first read. The content earns its place, yet the structure could be broken into shorter sentences without losing information.

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 must carry return-value semantics, and it does: it names the Direct and Indirect columns, explains what Last Transaction means versus Holding, and flags the stale-date/zero-share edge case. For a three-parameter read tool, nothing an agent needs in order to call or interpret it is missing.

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%, so ticker, offset and maxResults are already fully documented in the schema, including clamping and paging rules. The description adds only the ranking definition ("ranked by total shares held") and restates the default of 30, which marginally clarifies what offset is paging over but does not extend the parameters themselves.

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 opens with a specific verb and resource ("Get a summary of insider ownership for a stock") plus the ranking key ("ranked by total shares held"), and it explicitly contrasts itself with GetInsiderTransactions. An agent can distinguish it from the sibling without inspecting either schema.

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?

It states the intended purpose ("understand the insider ownership structure of a company") and names the alternative for a different need ("use GetInsiderTransactions for the underlying trades"). It also warns that former insiders may linger with stale dates or zero shares, though it gives no explicit when-not-to-use conditions beyond that single routing rule.

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.