Equibles

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. 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.

Input Schema

Name	Required	Description
`offset`	No	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.
`ticker`	Yes	Company ticker symbol (e.g., AAPL, MSFT)
`maxResults`	No	Maximum number of insiders to return (default: 30, max: 500; values outside 1-500 are clamped)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

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."

Changed1 schema field changedAug 9, 2026

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"
+}

First observedJul 19, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description goes well beyond that: it explains the aggregation methodology (direct vs indirect vehicles, derivative exclusion, split-basis restatement), and discloses real caveats — vehicles absent from the newest filing are not counted, and former insiders may linger with stale dates or zero shares. That is exactly the kind of data-quality context an agent needs to interpret results.

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 the sibling routing are front-loaded, and the dense methodology is placed after the headline so an agent can stop reading early. It is somewhat long and the middle clause chains many qualifiers, but nearly every sentence carries information an agent would otherwise have to infer.

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-value burden — and it does, specifying the ranked ordering, the Direct/Indirect columns, the split-basis restatement, and the row cap tied to maxResults. Combined with the parameter coverage, nothing an agent needs to call or interpret this tool 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%, including detailed pagination semantics for offset and clamping rules for maxResults, so the schema already does the heavy lifting. The description only restates the default of 30, adding no meaning beyond the structured fields. Baseline 3 is appropriate.

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 precise verb+resource ('summary of insider ownership for a stock, ranked by total shares held') and immediately qualifies the scope with the data source (SEC Form 3/4/5 closing balances). It also differentiates from the nearest sibling by naming GetInsiderTransactions for underlying trades, so an agent can route without opening any 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 gives an explicit use case ('understand the insider ownership structure of a company') and names one alternative (GetInsiderTransactions) with the condition that selects it. It does not, however, disambiguate against other ownership-adjacent siblings such as GetBeneficialOwnership, GetTopHolders or GetAllHolders, so the routing guidance is clear but incomplete.

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

All Equibles tools Inspect

Try in Browser