SEC EDGAR MCP

get_insider_summary

Summarize insider trading activity for any company by ticker or CIK, returning filing counts, unique insiders, and recent transactions within a chosen time window.

Instructions

Get a summary of insider trading activity.

Args: identifier: Company ticker symbol or CIK number days: Number of days to analyze (default: 180)

Returns: Summary with filing counts by form type, unique insiders, and recent activity.

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": {
      "identifier": "<identifier>"
    },
    "name": "get_insider_summary"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No
`identifier`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.8May 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The description discloses that it returns a summary with specific fields, but it does not mention any behavioral aspects such as read-only nature, data freshness, or if it requires any special permissions. With no annotations, this is adequate but not detailed.

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?

The description is very concise with four sentences, clearly organized with 'Args' and 'Returns'. Every sentence adds value without redundancy.

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 no output schema, the description adequately explains the return structure. However, it could be more complete by noting the scope of insider activity (e.g., recent filings) and how it differs from other insider tools. Overall, sufficient for a summary tool.

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?

The description explains that 'identifier' is a ticker or CIK number and 'days' is the number of days to analyze with a default of 180. This adds meaning beyond the schema, which only provides titles and types. Schema coverage is 0%, so the description compensates well.

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 clearly states the tool returns 'a summary of insider trading activity', which is a specific verb+resource. It specifies the output includes filing counts, unique insiders, and recent activity, distinguishing it from detailed transaction tools like get_insider_transactions.

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?

No guidance is provided on when to use this tool versus sibling tools like analyze_insider_sentiment or get_insider_transactions. There is no mention of when-not-to-use or alternatives.

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