Skip to main content
Glama
sec-edgar-fda-b2b-mcp

sec-edgar-fda-b2b-mcp

get_sec_form4_insider_trades

Read-onlyIdempotent

Track SEC Form 4 insider buying and selling by executives and directors. Query tickers to get parsed open-market transactions with insider role, shares, price, total value, filing date, and filing URL.

Instructions

Fetch parsed US SEC EDGAR Form 4 insider buying (P) and selling (S) transactions.

Use this tool to track executive (CEO, CFO, Director) open-market stock purchases and sales.
Returns a JSON array of up to 25 filing records containing ticker, companyName, insiderName,
insiderRole, transactionCode, shares, pricePerShare, totalValue, filingDate, and filingUrl.
Requires the APIFY_TOKEN environment variable.

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": {
      "tickers": "<tickers>"
    },
    "name": "get_sec_form4_insider_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickersYesList of US stock ticker symbols to query (e.g., ['NVDA', 'AAPL', 'TSLA']).
max_filings_per_tickerNoMaximum number of recent SEC Form 4 filings to return per ticker (1-50).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / max_filings_per_ticker / description
      Added value: +"Maximum number of recent SEC Form 4 filings to return per ticker (1-50)."
    • addedInput schema / properties / max_filings_per_ticker / maximum
      Added value: +50
    • addedInput schema / properties / max_filings_per_ticker / minimum
      Added value: +1
    • addedInput schema / properties / tickers / description
      Added value: +"List of US stock ticker symbols to query (e.g., ['NVDA', 'AAPL', 'TSLA'])."
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description usefully adds the APIFY_TOKEN auth requirement and a result cap, but 'up to 25 filing records' sits awkwardly against a schema that permits 50 filings per ticker across multiple tickers, creating ambiguity about actual return volume and pagination.

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?

Four short sentences, front-loaded with purpose, then use case, then output shape and auth requirement. Minimal waste; the enumerated return fields are somewhat redundant given an output schema exists, and the 25-record claim is a slightly noisy detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, open-world data fetch with an output schema present, the definition covers purpose, auth, and return shape adequately. The remaining gap is the inconsistency between the stated 25-record cap and a schema allowing up to 50 filings per ticker for multiple tickers, which leaves the true result size uncertain.

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 both parameters (tickers, max_filings_per_ticker) are fully documented in the schema, setting the baseline at 3. The description adds only the notion of per-ticker multiplicity and a record cap, and the latter conflicts with the documented maximum, so it does not meaningfully enrich parameter meaning.

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?

States a specific verb ('Fetch parsed') plus exact resource ('US SEC EDGAR Form 4 insider buying (P) and selling (S) transactions'), which is clearly distinct from the institutional 13F sibling. It does not explicitly contrast with siblings, but the Form 4 resource framing makes the scope unambiguous.

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?

'Use this tool to track executive (CEO, CFO, Director) open-market stock purchases and sales' gives a concrete use case and narrows scope to open-market P/S codes, excluding, for example, grants or option exercises. No explicit when-not conditions or named alternatives are given, keeping it short of a 5.

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