Skip to main content
Glama

Insider ownership filings (Forms 3/4/5)

get_insider_trades
Read-only

List normalized SEC insider ownership filings (Form 4 transactions, plus Form 3 initial statements and Form 5 annual statements — 3/5 live-forward since 2026-09-23), newest first: non-derivative and derivative transaction legs, holdings, owner roles (director/officer/10% owner), footnotes, and amendment (/A) links. Numeric values are strings exactly as filed; every object carries 'accession' and 'filed_date'. Filter by issuer ticker, issuer CIK, reporting-owner CIK (owner_cik — one insider's filings across every issuer), form_type, or since-date. Returns a {data, total, limit, offset} envelope for paging. For day- or market-wide sweeps, set compact=true: one summary row per filing (issuer, owners with roles, leg counts, open-market purchase/sale share + as-filed dollar aggregates) and up to 100 rows per call instead of 25 — then fetch any filing's full detail with get_insider_filing. Hosted and already normalized — no EDGAR crawling, parsing, or local install needed.

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

Input Schema

NameRequiredDescriptionDefault
cikNoSEC CIK number, digits only (leading zeros optional).
limitNoRows to return — max 25 for full filing objects, 100 with compact=true.
sinceNoOnly filings filed on/after this date (YYYY-MM-DD).
untilNoOnly filings filed on/before this date (YYYY-MM-DD) — with since, a fixed reproducible window.
offsetNoRows to skip — page through 'total' with limit+offset.
tickerNoIssuer ticker symbol, e.g. KMI. Case-insensitive; matches each symbol of a multi-listed filing ('WSO; WSOB' matches WSO).
compactNotrue returns one compact survey row per filing — issuer, owners with roles, non-derivative/derivative leg counts, and open-market (code P/S) share + as-filed dollar aggregates computed from the filed numbers — and raises the row cap to 100. Sized for day- or market-wide sweeps; fetch full detail per filing with get_insider_filing.
form_typeNo3 = initial ownership, 4 = transactions, 5 = annual statement; /A = amendment. Forms 3/5 are live-forward since 2026-09-23.
owner_cikNoReporting owner (insider) CIK, digits only — one person or entity's filings across every issuer. Owner CIKs appear in each filing's reporting_owners[].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / compact
      Added value: +{
      +  "default": false,
      +  "description": "true returns one compact survey row per filing — issuer, owners with roles, non-derivative/derivative leg counts, and open-market (code P/S) share + as-filed dollar aggregates computed from the filed numbers — and raises the row cap to 100. Sized for day- or market-wide sweeps; fetch full detail per filing with get_insider_filing.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Rows to return (max 25 on this endpoint)."New value: +"Rows to return — max 25 for full filing objects, 100 with compact=true."
    • changedInput schema / properties / limit / maximum
      Previous value: -25New value: +100
  2. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Issuer ticker symbol as filed, e.g. KMI. Case-insensitive exact match."New value: +"Issuer ticker symbol, e.g. KMI. Case-insensitive; matches each symbol of a multi-listed filing ('WSO; WSOB' matches WSO)."
  3. Changed2 schema fields changed
    • changedInput schema / properties / form_type / description
      Previous value: -"4 = original filing, 4/A = amendment."New value: +"3 = initial ownership, 4 = transactions, 5 = annual statement; /A = amendment. Forms 3/5 are live-forward since 2026-09-23."
    • changedInput schema / properties / form_type / enum
      Previous value: -[
      -  "4",
      -  "4/A"
      -]New value: +[
      +  "3",
      +  "3/A",
      +  "4",
      +  "4/A",
      +  "5",
      +  "5/A"
      +]
  4. Changed1 schema field changed
    • addedInput schema / properties / owner_cik
      Added value: +{
      +  "description": "Reporting owner (insider) CIK, digits only — one person or entity's filings across every issuer. Owner CIKs appear in each filing's reporting_owners[].",
      +  "pattern": "^\\d{1,10}$",
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  6. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint/destructiveHint=false, it discloses non-obvious behavior: numeric values are strings exactly as filed, every object carries accession and filed_date, row caps of 25 (full) vs 100 (compact), and a {data, total, limit, offset} envelope. It also flags a temporal coverage caveat (Forms 3/5 live-forward since 2026-09-23) and that no EDGAR crawling or local install is required.

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 the tool returns, then filtering, then paging, then the compact-mode alternative — a sensible information order. It is a dense single block and some clauses (e.g. 'Hosted and already normalized — no EDGAR crawling...') are promotional filler, but nothing is materially redundant.

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?

With no output schema, the description steps in to describe the return envelope, the per-record fields (accession, filed_date), and the compact-row shape. Together with the 9 parameters and the two-mode paging behavior, an agent has enough to call this correctly on the first attempt.

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 the schema already documents every parameter including compact, owner_cik, and form_type. The description restates those meanings (owner_cik = one insider across every issuer; compact raises the row cap) rather than adding syntax, defaults, or edge cases not already present, so it sits at the baseline.

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?

Opens with a specific verb and resource ('List normalized SEC insider ownership filings') and enumerates the content: non-derivative/derivative legs, holdings, owner roles, footnotes, amendment links. It also implicitly distinguishes itself from the sibling get_insider_filing by describing itself as the multi-row listing that feeds into per-filing detail retrieval.

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

Usage Guidelines5/5

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

Gives explicit routing: use compact=true for 'day- or market-wide sweeps' and then 'fetch any filing's full detail with get_insider_filing'. It also names the supported filter axes (ticker, issuer CIK, owner_cik, form_type, since) so the agent knows how to narrow rather than sweep.

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.

Resources