Skip to main content
Glama

List the latest Form 4 insider trades of a US company

sec_insiders
Read-only

The latest Form 4 insider transactions of a US company (ticker, CIK or name): insider name and role, transaction date, code (P buy, S sell, A grant, M exercise, F tax withholding), shares, price and shares owned afterwards, with the filing link. Common-stock lines only; derivative grants are not listed. Related tools on this server, for a different need: sec_13f when you need to return the latest Form 13F-HR holdings; sec_events when you need to list a US company's latest 8-K filings and their items. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "sec_insiders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoFilings to read, 1 to 10 (default 5)
companyYesTicker, CIK or company name

Output Schema

NameRequiredDescriptionDefault
noteNo
countNo
sourceNo
companyNo
checkedAtNo
disclaimerNo
filingsReadNo
transactionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real context the annotations cannot: common-stock lines only with derivative grants excluded, and a pay-per-call model ($0.003 per successful call via x402 in USDC, failed calls not charged). The coverage exclusion is the most valuable disclosure since it prevents misreading an incomplete insider picture; only a lack of any note on latency or data currency holds it below a 5.

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?

Purpose is front-loaded and every block (field list, code glossary, coverage caveat, sibling routing, pricing) serves a distinct decision. The inline transaction-code glossary (P/S/A/M/F) is arguably redundant given that an output schema exists, and the dense parentheticals make it heavier than it needs to be.

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?

For a read-only, two-parameter lookup with an output schema, the description covers what the tool does, what it returns in outline, what it excludes (derivatives), what it costs, and where to go instead. The remaining gap is minor: no guidance on what a caller sees when multiple insiders or filings are returned relative to 'limit'.

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 100%, with both 'company' (ticker, CIK or company name) and 'limit' (1 to 10, default 5) fully documented in the schema, so the baseline is 3. The description restates the accepted identifier forms but adds no new constraint such as what happens with ambiguous names or how 'limit' interacts with multi-owner filings.

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 opens with a specific verb and resource ('latest Form 4 insider transactions of a US company') plus accepted identifiers (ticker, CIK or name), and enumerates the returned fields. It also names the sibling tools sec_13f and sec_events by the resource they cover, so an agent can separate this tool from its neighbors without opening a schema.

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 gives explicit routing guidance: 'sec_13f when you need to return the latest Form 13F-HR holdings' and 'sec_events when you need to list a US company's latest 8-K filings'. That is clear alternative selection, but there is no statement of when this tool is the wrong choice beyond those two named cases, and no noted preconditions such as whether the company must be US-listed.

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