sec-ai

Overview Schema Source Related Servers Discussions Admin

get_insider_transactions

Read-onlyIdempotent

Fetch SEC insider trading transactions (Forms 3, 4, 5) by ticker to review insider buying, selling, and ownership activity.

Instructions

Get insider trading transactions (Forms 3, 4, 5) for a company.

Args: ticker: Stock ticker symbol limit: Number of transactions to return

Returns: Dictionary containing insider transaction information

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": {
      "ticker": "<ticker>"
    },
    "name": "get_insider_transactions"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`ticker`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 21, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety and repeatability profile is covered. The description adds that the tool returns insider transaction information and names the relevant SEC forms, but it does not discuss rate limits, authentication, or characteristics of the returned data beyond the generic return statement.

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?

The description is short and front-loaded with the core purpose. The Args and Returns sections are somewhat boilerplate but still compact and not wasteful.

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?

Given that the tool is a simple read-only lookup with only two parameters, rich annotations, and an output schema, the description provides enough context to invoke it correctly. The main missing element is guidance on sibling selection, which is not required for correct invocation but would improve routing.

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 0%, so the description must compensate for undocumented parameters. It explains that ticker is a stock ticker symbol and limit is the number of transactions to return, which meaningfully clarifies both parameters, but it omits the default value of 20 and any limits or formatting details for ticker.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action and resource: retrieving insider trading transactions, specifically Forms 3, 4, and 5, for a company. It is clear what the tool does, though it does not explicitly differentiate itself from related sibling tools such as get_beneficial_ownership.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus related alternatives, nor does it mention any preconditions or exclusions. The agent must infer its role from the name and sibling list alone.

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