Skip to main content
Glama

Insider purchases and sales by quarter

get_insider_trading
Read-only

Returns what executives, directors and 10% owners of the tracked companies bought and sold on Form 4 in one quarter: totals, the largest sellers and buyers (role, company, trades, shares still held, filing), the companies most sold and bought by their insiders, totals by role and month, and new insiders. Default: the last closed quarter; quarter: 'current' for the one in progress; quarters from Q3 2024. Only purchases and sales count: method and caveats say what is and is not. For one company's insiders, use get_ownership; for one person, pass holder to get_holders.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows per list (default 8, max 25).
quarterNo'latest' (default: the last closed quarter), 'current' (the quarter in progress, to date) or a quarter such as 'q3-2026' (from 'q3-2024').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +25
    • addedInput schema / properties / limit / minimum
      Added value: +1
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and closed-world scope, so safety is covered structurally. The description adds non-obvious behavioral detail: only purchases and sales count, with `method` and `caveats` explaining inclusions/exclusions, and it discloses the data-range constraint. It does not cover pagination/ordering behavior, keeping it at 4.

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 resource and payload, then defaults, then alternative-tool routing — a sensible order with no filler. It is dense and a single long sentence chain, which slightly hurts scanability but every clause carries information.

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 enumerating the return contents (totals, largest sellers/buyers with role/company/trades/shares held/filing, most sold and bought companies, totals by role and month, new insiders). Combined with full param coverage and clear annotations, an agent has everything needed to call it correctly.

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 is 3; the description goes further by restating the quarter semantics in context ('Default: the last closed quarter; `quarter: 'current'` for the one in progress') and noting the historical floor. The `limit` parameter is left entirely to the schema, which is acceptable given full coverage.

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 ('Returns what executives, directors and 10% owners ... bought and sold on Form 4 in one quarter') and enumerates the payload contents, so the agent knows exactly what it retrieves. It also names the relevant siblings (get_ownership, get_holders) so the tool is distinguishable 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 explicit routing: 'For one company's insiders, use get_ownership; for one person, pass `holder` to get_holders.' It also defines defaults (last closed quarter) and the range floor (Q3 2024), so there is no ambiguity about when this tool is the right choice.

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.