Skip to main content
Glama
Sign In

InsiderRadar

by nl.insiderradar
OverviewDiscussionsAdmin

Companies with the most insider buying or selling (SEC Form 4)

top_insider_activity
Read-onlyIdempotent

Across the whole US market: the companies whose insiders bought (or sold) the most in the open market over a period, ranked by USD value. Each company has the total value, shares, number of filings and insiders, the share of the value that was under a Rule 10b5-1 plan, and its largest filing with source_url. Planned trades are left out by default (planned=exclude) and the answer says so. Common and other non-derivative shares only (Form 4 Table I). Default: the last 7 days; at most 90 days, and at most 31 for periods before 2026-06-15.

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

Input Schema

NameRequiredDescriptionDefault
toNoLast filing date, as YYYY-MM-DD (included).
daysNoLook back this many days from today. Default 7. Leave out when you give from.
fromNoFirst filing date, as YYYY-MM-DD (included).
roleNoOnly filings by a director, an officer, or an owner of more than 10% of the company.
sideNobuy = open-market purchases (default), sell = open-market sales.
limitNoHow many companies to return. Default 10.
plannedNoRule 10b5-1 trading plans: a trade marked planned_trade=true was made under a plan the insider set up in advance, so its timing was fixed earlier. exclude = leave planned trades out, only = only planned trades, all = both. The checkbox exists on Form 4 since April 2023; older filings have planned_trade=null and count as not planned. Default exclude.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real substance on top: planned trades are omitted by default and 'the answer says so', only Form 4 Table I common/non-derivative shares count, and the date-range ceiling shrinks to 31 days for older periods. It also enumerates the per-company metrics returned (value, shares, filings, insiders, 10b5-1 share, largest filing with source_url).

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 the core purpose, then the return contents, then the default/exclusion rules and the date constraints — a sensible order with no filler. The middle sentence stacks many returned fields into one long clause, which costs a little readability.

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 no output schema, the description compensates by listing exactly what each row contains, including source_url for provenance. Combined with the coverage of defaults, exclusions, and date ceilings, an agent has everything needed to call it and interpret the result.

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 the baseline is 3, but the description adds meaning the schema does not carry: the 31-day limit for periods before 2026-06-15, the planned=exclude default behavior, and the Table I share-type restriction. The remaining parameters (role, side, limit) are only echoed at a high level.

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?

States a specific verb and resource plus scope: 'Across the whole US market: the companies whose insiders bought (or sold) the most in the open market over a period, ranked by USD value.' The market-wide ranking scope makes it distinguishable from search_insider_transactions (per-transaction lookup) and summarize_issuer_insiders (per-issuer) even though no sibling is named outright.

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?

Gives concrete operating context: default window of the last 7 days, a 90-day cap (31 days for periods before 2026-06-15), and the default planned=exclude. It never explicitly routes the agent to a sibling tool or states when not to use this one, so usage is clear but not exhaustive.

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

All InsiderRadar toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources