Skip to main content
Glama

Search insider transactions (SEC Form 4 and the European registers)

search_insider_transactions
Read-onlyIdempotent

Find insider transactions reported to the SEC on Form 4, from 2020 to today (country=US, the default), or in the registers of the Netherlands (AFM), Germany (BaFin), Belgium (FSMA), Sweden (FI) and Spain (CNMV) with country=NL, DE, BE, SE or ES, the five European registers together with country=EU, or all of them with country=all. European rows are one line of the regulator's register each, in the currency of the filing with a euro value next to it, and every row names its source (source, source_url); cite it when you use a row. For Form 4: Filter by ticker, company, insider name, role, buy or sell, a date range, a minimum value and Rule 10b5-1 plans; sort newest first or by largest value. By default the lines of one filing with the same transaction code are combined into one row (total shares, weighted average price, total value, number of lines). For 'the largest recent insider purchases' use type=buy and sort=largest_value. Each row has the insider and their role, the dates, shares, price, value in USD, whether it was a planned trade, source_url (the filing at the SEC) and company_url (our company page, when there is one). Open-market purchases and sales since 1 July 2026 also carry the latest price and the change from the price in the filing to that latest price: a measurement of the share price, not advice.

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": "search_insider_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast filing date, as YYYY-MM-DD (included).
daysNoLook back this many days from today. Default 90. Leave out when you give from.
fromNoFirst filing date, as YYYY-MM-DD (included).
roleNoOnly filings by a director, an officer, or an owner of more than 10% of the company.
sortNonewest = newest filing first (default); largest_value = highest value in USD first.
typeNobuy = open-market purchases (code P), sell = open-market sales (code S), all = every transaction (also awards, option exercises, tax withholding, gifts). Default all.
limitNoHow many rows to return. Default 20.
issuerNoPart of the issuer's company name, e.g. Nvidia. Use ticker when you know it.
tickerNoThe issuer's exchange ticker, e.g. NVDA (case does not matter). Matched on the company's SEC identifier (CIK), so filings made under an earlier ticker are included (META also finds the FB years).
countryNoWhich register: US = SEC Form 4 since 2020 (default); NL = the Dutch AFM registers; DE = BaFin (Germany); BE = FSMA (Belgium); SE = Finansinspektionen (Sweden); ES = CNMV (Spain); EU = the five European registers together (for a question about Europe, sorted on the euro value with sort=largest_value); all = every register together, as the InsiderRadar register page shows it (US filings there start on 1 July 2026; earlier ones with country=US). For anything but US, ticker, role, planned, group_by_filing and min_value_usd do not apply: use issuer for the company and min_value_eur for a minimum amount.
insiderNoPart of the reporting person's name as filed, e.g. Huang. SEC filings usually write the last name first (HUANG JEN HSUN).
plannedNoRule 10b5-1 trading plans: the Form 4 box says at least one transaction in the filing was made under a plan the insider set up in advance, so its timing was fixed earlier. The box is per filing: an open-market purchase or sale in such a filing carries planned_trade=true, another line (a gift, a conversion) planned_trade=null with a note. The filter works on the filing's box: exclude = leave out every line of a filing with the box ticked, only = only those lines, all = both. The checkbox exists on Form 4 since April 2023; older filings have planned_trade=null and count as not planned. Default all.
min_value_eurNoOnly rows worth at least this many euros, converted at the ECB reference rate of the trade date. For any country except US.
min_value_usdNoOnly rows worth at least this many US dollars (shares × price as filed).
group_by_filingNotrue (default) = one row per filing and transaction code; false = every line of the filing as its own row.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Which register: US = SEC Form 4 since 2020 (default); NL = the Dutch AFM registers; DE = BaFin (Germany); BE = FSMA (Belgium); SE = Finansinspektionen (Sweden); ES = CNMV (Spain); EU = the five European registers together (for a question about Europe, sorted on the euro value with sort=largest_value); all = every register together, as the InsiderRadar register page shows it (US filings there start on 15 June 2026). For anything but US, ticker, role, planned, group_by_filing and min_value_usd do not apply: use issuer for the company and min_value_eur for a minimum amount."New value: +"Which register: US = SEC Form 4 since 2020 (default); NL = the Dutch AFM registers; DE = BaFin (Germany); BE = FSMA (Belgium); SE = Finansinspektionen (Sweden); ES = CNMV (Spain); EU = the five European registers together (for a question about Europe, sorted on the euro value with sort=largest_value); all = every register together, as the InsiderRadar register page shows it (US filings there start on 1 July 2026; earlier ones with country=US). For anything but US, ticker, role, planned, group_by_filing and min_value_usd do not apply: use issuer for the company and min_value_eur for a minimum amount."
    • changedInput schema / properties / planned / description
      Previous value: -"Rule 10b5-1 trading plans: a trade marked planned_trade=true was made under a plan the insider set up in advance, so its timing was fixed earlier. exclude = leave planned trades out, only = only planned trades, all = both. The checkbox exists on Form 4 since April 2023; older filings have planned_trade=null and count as not planned. Default all."New value: +"Rule 10b5-1 trading plans: the Form 4 box says at least one transaction in the filing was made under a plan the insider set up in advance, so its timing was fixed earlier. The box is per filing: an open-market purchase or sale in such a filing carries planned_trade=true, another line (a gift, a conversion) planned_trade=null with a note. The filter works on the filing's box: exclude = leave out every line of a filing with the box ticked, only = only those lines, all = both. The checkbox exists on Form 4 since April 2023; older filings have planned_trade=null and count as not planned. Default all."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses default row grouping (one row per filing and transaction code with total shares, weighted average price, total value), that European rows are single register lines in filing currency with a euro equivalent, the source/source_url citation obligation, and the per-filing nature of the 10b5-1 box including null handling for pre-April-2023 filings. The price-change field is explicitly framed as a measurement, not advice, which is meaningful behavioral context.

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?

The purpose and country routing are front-loaded and nearly every sentence carries operative detail. It is a dense single block of prose, though, and the Form 4 filter list and output-field list could be tightened or split for scanability 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?

For a 15-parameter, zero-required search tool with no output schema, the description covers defaults (country=US, grouping on, 90-day window implied by schema), filter applicability per register, and the fields each returned row contains. An agent has enough to construct a correct call and interpret the response without further probing.

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 would be 3, but the description adds cross-parameter meaning the schema cannot: which filters are inapplicable for non-US registers, the EU aggregation mode being euro-sorted, and the ticker-to-CIK matching that pulls in historical tickers. Most per-parameter definitions are duplicated from the schema rather than extended, which caps it below 5.

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 ('Find insider transactions') and immediately scopes it to SEC Form 4 since 2020 plus five named European registers, so an agent knows exactly what corpus is searched. It also distinguishes the register variants via the country values rather than leaving that to inference.

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?

Gives concrete when-to-use routing ('For "the largest recent insider purchases" use type=buy and sort=largest_value') and warns that ticker, role, planned, group_by_filing and min_value_usd do not apply outside the US, pointing to issuer and min_value_eur instead. It does not contrast itself against siblings such as top_insider_activity or summarize_issuer_insiders, so the alternative-selection story is only partial.

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