Skip to main content
Glama

Arkanum Data: SEC insider trades

Search insider trades

search_insider_trades
Read-only

Open-market insider buys and sales from SEC Form 4 filings, newest filing first, each linked to its filing. Free keys see the last 30 days up to yesterday; Hobby and Pro also see today's filings (hourly) and get activity_score, insider_pattern and reading (the facts that matter in the filing). Filing data only: no stock prices or returns. This covers the last 30 days only: for older trades use search_insider_history.

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

Input Schema

NameRequiredDescriptionDefault
sideNo
limitNo
cursorNonext_cursor from a previous call
tickerNoStock ticker, e.g. AAPL
plannedNotrue: only pre-planned 10b5-1 trades; false: only unplanned
filed_toNoYYYY-MM-DD
min_valueNoMinimum trade value in dollars
filed_fromNoYYYY-MM-DD
insider_cikNoThe insider's SEC ID (CIK)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description adds the operationally important traits an agent cannot get elsewhere: newest-filing-first ordering, tier-based access windows (free keys see through yesterday, paid tiers see today's hourly filings), and which response fields are tier-gated. It also discloses that data is filing-derived with no price/return data, preventing a wrong-tool call.

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?

What the tool returns and its ordering lead, followed by access-tier caveats, then the data-type exclusion and the 30-day boundary with the alternative. Three dense sentences with no filler; every clause carries information an agent needs to pick or scope the call.

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

Completeness5/5

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

With nine optional parameters, no output schema, and thin annotations, the description supplies the missing context: data provenance, result ordering, freshness differences by tier, the gated response fields, and the hard 30-day window. Nothing material for correct invocation or tool selection is left unstated.

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 78%, so the schema already documents most parameters (ticker, filed_from/filed_to format, cursor, planned, min_value, insider_cik). The description reinforces the implicit 30-day bound on the date parameters and the buy/sale split, but adds no syntax or constraint detail beyond the schema. Baseline 3 applies.

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?

Names a specific verb and resource (open-market insider buys and sales) plus the source system (SEC Form 4), and explicitly fences off the sibling that covers older data: 'for older trades use search_insider_history.' An agent can distinguish this from search_insider_history and latest_insider_trades without opening any schema.

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?

Gives an explicit when-to-use-elsewhere rule with the named alternative (older than 30 days → search_insider_history) and an explicit scope exclusion ('Filing data only: no stock prices or returns'), which steers price-oriented queries away. Both the boundary and the alternative are stated rather than inferred.

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