Skip to main content
Glama
theodor90

form4api-mcp

get_transactions

Read-only

Search SEC Form 4 insider transactions with filters for ticker, insider, transaction type, and date range. Exclude automated 10b5-1 plans to focus on discretionary trades.

Instructions

Search SEC Form 4 insider transactions. Filter by ticker, insider, transaction type, date range, and more. Use exclude_10b5=true for discretionary-only signal analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd date in ISO 8601 format, e.g. 2026-12-31
cikNoCompany CIK number
codeNoSEC transaction code. P=purchase, S=sale, A=award, M=option exercise, F=tax withholding, D=disposition
fromNoStart date in ISO 8601 format, e.g. 2026-01-01
pageNoPage number for pagination
codesNoComma-separated list of SEC transaction codes to include, e.g. "P,S". Multi-code superset of `code`.
tickerNoStock ticker symbol, e.g. 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 (max 100)
max_valueNoMaximum trade value in USD (shares × price). Pro plan or higher.
min_valueNoMinimum trade value in USD (shares × price). Pro plan or higher.
max_sharesNoMaximum number of shares. Pro plan or higher.
min_sharesNoMinimum number of shares. Pro plan or higher.
insider_cikNoInsider CIK number
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.
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's behavioral contribution is minimal. It adds no new insights about side effects, authentication, or rate limits beyond what the schema and annotations already provide.

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?

Description is two sentences with clear front-loading of the main action and key filter category, then a specific recommendation. No unnecessary words, perfectly sized for the tool's complexity.

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 the high parameter count and lack of output schema, the description adequately covers the tool's purpose and offers a key usage hint. It could mention pagination or result format but is not critically incomplete.

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% for all 19 parameters, so the baseline is 3. The description offers only one additional usage tip (exclude_10b5) beyond the schema, which adds marginal value.

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?

Description clearly states the verb 'Search' and resource 'SEC Form 4 insider transactions', and lists key filters. It distinguishes from siblings like get_insider_transactions by specifying the Form 4 scope, although not explicitly contrasting.

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?

Provides explicit guidance on using exclude_10b5 for discretionary-only signal analysis, and mentions filtering capabilities. However, it does not specify when not to use this tool or compare to alternatives like get_insider_transactions or get_signals.

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