Skip to main content
Glama
brechanbech

SEC EDGAR MCP

by brechanbech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Remote

Insider Transactions

sec_insider_transactions
Read-only

Retrieve a company's insider transactions from SEC Forms 3, 4, 5 and 144: who bought or sold, when, share counts and prices, with transaction codes and footnotes explained in plain language.

Instructions

Get insider transactions (SEC Forms 3, 4 and 5) for a company by ticker — who bought or sold, when, how many shares and at what price, with each insider's name and role. Reads the filings themselves, so results include the SEC transaction code expanded into plain language and any explanatory footnotes: this matters because a 'F' is shares withheld to cover tax on vesting, not a market sale. Form 3 reports initial holdings rather than transactions, so its facts appear under 'holdings'; a Form 3 from an insider who owns nothing yet has empty holdings and 'no_securities_owned': true. With form_type '144', returns Form 144 notices instead: an affiliate's notice of a proposed sale, filed when the order is placed and before the Form 4 that reports the executed trade. Each gives the seller and their relationship to the company, the shares and market value to be sold, the broker and approximate date, how the shares were acquired, any Rule 10b5-1 plan adoption date, and sales in the past three months. A notice is an intent to sell, not a completed sale. Reads 5 filings by default and at most 10 per call; pass 'next_offset' back as 'offset' for older ones.

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of insider filings to read (default 5, max 10). Each filing is one insider's report.
offsetNoNumber of most-recent matching filings to skip, for paging back (default 0). Pass the previous response's 'next_offset'.
tickerYesStock ticker, e.g. AAPL, or the company's CIK, e.g. 1163302, for one with no current ticker (delisted, acquired or renamed)
form_typeNoOptional filter: '4' (changes in ownership — the usual choice), '3' (initial ownership, holdings only), '5' (annual catch-up) or '144' (notice of a proposed sale, filed before the Form 4 that reports it). Omit for forms 3, 4 and 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.10.0
    • changedInput schema / properties / form_type / description
      Previous value: -"Optional filter: '4' (changes in ownership — the usual choice), '3' (initial ownership, holdings only) or '5' (annual catch-up). Omit for all three."New value: +"Optional filter: '4' (changes in ownership — the usual choice), '3' (initial ownership, holdings only), '5' (annual catch-up) or '144' (notice of a proposed sale, filed before the Form 4 that reports it). Omit for forms 3, 4 and 5."
    • changedInput schema / properties / form_type / enum
      Previous value: -[
-  "3",
-  "4",
-  "5"
-]New value: +[
+  "3",
+  "4",
+  "5",
+  "144"
+]
  2. Changed3 schema fields changedv0.7.0
    • changedInput schema / properties / limit / description
      Previous value: -"Number of insider filings to read (default 5, max 20). Each filing is one insider's report."New value: +"Number of insider filings to read (default 5, max 10). Each filing is one insider's report."
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Number of most-recent matching filings to skip, for paging back (default\n0). Pass the previous response's 'next_offset'.",
+  "format": "uint64",
+  "minimum": 0,
+  "type": "integer"
+}
    • changedInput schema / properties / ticker / description
      Previous value: -"Stock ticker symbol"New value: +"Stock ticker, e.g. AAPL, or the company's CIK, e.g. 1163302, for one with no\ncurrent ticker (delisted, acquired or renamed)"
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description explains that it reads filings directly, expands SEC transaction codes into plain language, and preserves footnotes. It also discloses important edge cases: Form 3 holdings semantics, empty holdings with 'no_securities_owned': true, and that Form 144 notices are intents to sell rather than completed trades.

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

Conciseness5/5

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

The description is front-loaded with the core purpose and then adds only operationally important caveats about SEC form semantics, Form 144 notices, and paging. Despite being dense, every sentence contributes useful context for correctly invoking and interpreting the tool.

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?

For a read-only SEC filings tool with no output schema, the description is complete enough to guide selection and interpretation. It covers return content, Form 3 and Form 144 special cases, code expansion, footnotes, default/max limits, and pagination.

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 the baseline is 3; however, the description adds meaningful semantics beyond the schema. It clarifies that Form 144 changes the returned data shape, that '4' is the usual form_type, that ticker may also be a CIK for companies without a current ticker, and that limit defaults to 5 and caps at 10 filings.

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?

The description states a specific verb and resource: get SEC Forms 3, 4 and 5 insider transactions by ticker, including who bought/sold, timing, shares, price, insider name and role. It is very clear about what the tool returns, but it does not explicitly distinguish itself from sibling tools such as sec_beneficial_ownership or sec_recent_filings.

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 clear usage context for form_type: '4' is the usual choice, '3' is holdings-only, '5' is annual catch-up, and '144' returns notices rather than executed trades. It also explains default limit and paging behavior. It does not, however, name alternative sibling tools or say when not to use this one.

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

Deploy Server

Other Tools