Skip to main content
Glama
theodor90

form4api-mcp

by theodor90

get_transactions

Read-only

Search SEC Form 4 insider transactions by ticker, insider CIK, date range, transaction code, and category. Filter by trade size on Pro plan for targeted analysis.

Instructions

Search SEC Form 4 insider transactions with rich filters: ticker, insider CIK, transaction code/category, date range, and (Pro+) trade-size thresholds. Returns transaction-level rows — shares, price, total value, transaction code, 10b5-1 flag, insider role flags. Use this for filtered or historical search across many companies/insiders; use get_recent_filings for an unfiltered live feed instead, or get_insider_transactions/get_company_insiders when you already have a specific insider or company. Free plan; min_value/max_value/min_shares/max_shares require Pro. Paginated, max 100/page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd date, inclusive, format YYYY-MM-DD (e.g. 2026-12-31). Filters on transactionDate.
cikNoCompany CIK number — SEC's numeric filer identifier, e.g. 0000320193. Leading zeros optional.
codeNoSingle SEC transaction code to filter to. P=open-market purchase, S=open-market sale, A=grant/award, M=option exercise, F=tax withholding on vesting, D=disposition to issuer, G=gift, C=conversion of derivative, J=other. Use `codes` instead to match more than one.
fromNoStart date, inclusive, format YYYY-MM-DD (e.g. 2026-01-01). Filters on transactionDate.
pageNo1-based page number. Defaults to 1.
codesNoComma-separated list of SEC transaction codes to include, e.g. "P,S" (see `code` for the letter meanings). Multi-code superset of `code`.
tickerNoStock ticker symbol, case-insensitive, e.g. AAPL or aapl.
categoryNoInclude only one category of transactions. open_market = P/S (the signal most users want); grants = award/comp noise; derivatives = option exercises etc.
per_pageNoResults per page. Defaults to 20, maximum 100.
max_valueNoMaximum trade value in USD (shares × price), inclusive. Requires Pro plan or higher — omitted or ignored on Free.
min_valueNoMinimum trade value in USD (shares × price), inclusive. Requires Pro plan or higher — omitted or ignored on Free.
max_sharesNoMaximum number of shares, inclusive. Requires Pro plan or higher — omitted or ignored on Free.
min_sharesNoMinimum number of shares, inclusive. Requires Pro plan or higher — omitted or ignored on Free.
insider_cikNoInsider CIK number — SEC's numeric filer identifier, e.g. 0001214128. Leading zeros optional.
significantNoIf true, preset = open-market trades only, no 10b5-1 plan trades, no derivatives. The "just show me real discretionary buys and sells" filter. Explicit params override it.
exclude_10b5NoIf true, exclude pre-scheduled 10b5-1 plan trades. Recommended for signal analysis — filters out automatic, non-discretionary trades.
exclude_codesNoComma-separated list of SEC transaction codes to exclude, e.g. "A,M,F,G" to drop grants, option exercises, tax withholding and gifts.
exclude_categoryNoExclude an entire category of transactions, e.g. exclude_category=derivatives drops all option-related rows.
exclude_derivativeNoIf true, drop derivative-security rows — the cleanest single "no options" switch.
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. Description adds that it is paginated with max 100 per page, and notes Pro plan requirements for some filters. It also lists return fields. No contradictions. Could add more on pagination behavior (e.g., total count) but overall good.

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?

Extremely concise: two sentences. First sentence covers main purpose and filters, second covers return fields, alternatives, plan notes, and pagination. Every sentence adds value.

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?

Given 19 parameters, no output schema, high complexity, the description provides comprehensive guidance: return fields, sibling distinctions, plan restrictions, pagination. It misses error handling or rate limits but annotations cover openWorldHint. Overall complete enough.

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 description coverage is 100%, so baseline is 3. Description adds useful context for parameters like 'codes' (multi-code superset), 'significant' (preset filter), and 'exclude_10b5' (recommended for signal analysis), going beyond what schema provides.

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?

Clearly states it searches SEC Form 4 insider transactions with rich filters, lists specific parameters (ticker, CIK, etc.), and distinguishes from siblings by naming alternative tools and their use cases.

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?

Explicitly specifies when to use this tool vs alternatives ('Use this for filtered or historical search... use get_recent_filings for an unfiltered live feed...') and mentions plan limitations for certain parameters.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/theodor90/form4api-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server