Skip to main content
Glama

finance.insider-trades

Retrieve recent SEC Form 4 insider transactions for any US public company by ticker. Get parsed details on insider name, relationship, transaction type, shares, and value.

Instructions

Recent SEC Form 4 insider transactions for a US public company by ticker. Returns parsed transactions: insider name + relationship (director, officer/title, 10%+ owner), date, SEC transaction code (P=purchase, S=sale, A=grant, D=disposition, M=exercise, F=tax-withholding, G=gift), security title, shares, price/share, total USD value, post-transaction balance, direct vs indirect ownership, derivative flag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax Form 4 filings to fetch + parse. Each is its own upstream call, bounded tight.
tickerYesUS stock ticker (case-insensitive).
Behavior4/5

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

With no annotations, the description carries full burden. It details the parsed output fields comprehensively (insider name, relationship, date, transaction code, shares, price, value, etc.). However, it does not specify the time range for 'recent' or address rate limits/pagination, though the limit parameter description (in schema) adds context about per-filing upstream calls.

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 description is a single paragraph that front-loads the tool's core purpose. The list of parsed fields is thorough but slightly verbose; however, every sentence adds value. No fluff.

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 no output schema, the description explains what the tool returns in detail. It covers all key data points. However, it omits edge cases like empty results, error handling, or authentication requirements. Still, it is largely complete for a data retrieval tool.

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 coverage is 100% with both parameters described. The main description reiterates the ticker input and implies the limit controls filing count, but adds no new semantic detail beyond the schema descriptions. Baseline 3 is appropriate.

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?

The description clearly states the tool retrieves recent SEC Form 4 insider transactions for a US public company by ticker. It lists the exact fields returned, making it highly specific and distinguishing it from sibling tools like finance.sec-filings or stocks.quote.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for insider transactions but does not explicitly differentiate it from alternatives like finance.sec-filings for broader SEC filings or finance.thirteen-f for institutional holdings. No when-to-use or when-not-to-use guidance is provided.

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/2s-io/sdk'

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