Skip to main content
Glama

Insider buys and sells (SEC Form 4)

find_insider_trades
Read-onlyIdempotent

Insider transactions from SEC Form 4 filings: who (officer, director, 10% owner) bought or sold a company's stock, with transaction code and plain label, shares, price, value, shares owned afterwards, dates and the SEC filing link. Requires at least one of ticker, insider or company. Defaults to open-market buys and sells over the last 7 days (max 14). Official EDGAR data. Max 10 rows per call.

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

Input Schema

NameRequiredDescriptionDefault
daysNoFiled in the last N days (default 7).
limitNoRows to return (default 10).
tickerNoStock tickers, e.g. NVDA. Max 3.
companyNoIssuer name contains. Max 3.
date_toNoWindow end, YYYY-MM-DD (default today).
insiderNoInsider name contains, e.g. "Cook". Max 3.
date_fromNoWindow start, YYYY-MM-DD (window max 14 days).
min_value_usdNoMinimum shares x price in USD.
transaction_typeNobuy = open-market purchases, sell = open-market sales, buy_sell (default) = both, all = every non-derivative code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds useful operational context — official EDGAR provenance, a 14-day window cap, and a 10-row-per-call ceiling — which is the kind of constraint annotations cannot express. It does not discuss pagination, latency, or error behavior beyond the row cap.

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?

Front-loaded with purpose, then the return payload, then the preconditions and defaults — a logical order with no filler. The return-field enumeration is long but earns its place because no output schema exists; the single dense block is the only mild readability cost.

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?

With no output schema, the description correctly compensates by listing returned fields, and with nine well-documented parameters plus annotations it covers the essentials an agent needs to call this correctly. Only minor gaps remain, such as result ordering and what happens when no filings match.

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 baseline would be 3, but the description adds a cross-parameter constraint the schema cannot express: at least one of ticker, insider, or company must be supplied (the schema declares zero required parameters). It also restates the default window and row limit in context, which helps an agent pick arguments.

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 opening clause names a specific verb and resource — insider transactions from SEC Form 4 filings — and immediately enumerates what a row contains (role, transaction code, shares, price, value, post-transaction holdings, dates, filing link). No sibling tool covers SEC insider filings, so the boundary is 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?

It states a hard precondition ('Requires at least one of ticker, insider or company') and explains the default behavior (open-market buys and sells, last 7 days, max 14). It stops short of naming when-not-to-use conditions or alternatives, but no sibling offers comparable functionality, so the gap is minor.

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