SEC EDGAR MCP

analyze_insider_sentiment

Analyze insider trading patterns and filing frequency for a company, returning a high, moderate, or low activity level and a recent activity summary.

Instructions

Analyze insider trading patterns and frequency.

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

Returns: Filing frequency analysis (high/moderate/low) and recent activity summary.

This provides frequency analysis only. For buy/sell sentiment, use analyze_form4_transactions to examine actual transaction details.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.8May 30, 2026

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses the tool's scope (frequency analysis only, not buy/sell) and what it returns. However, it does not mention any behavioral traits like data freshness or limitations beyond the scope note, which would elevate it to 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, well-structured with separate sections for Args, Returns, and a note. Every sentence adds value, and the note is strategically placed to clarify scope 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 explains return values (frequency analysis and activity summary), which is adequate. However, it lacks examples or specifics on data format, and the context signals indicate low schema coverage, so it could be slightly more detailed to achieve a perfect score.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, but the tool description compensates fully by explaining identifier is a ticker or CIK number and months is the analysis period with a default of 6. This adds meaningful context not present in the schema.

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 analyzes insider trading patterns and frequency, specifying it returns a filing frequency analysis (high/moderate/low) and recent activity summary. It distinguishes itself from the sibling tool analyze_form4_transactions by noting the difference, making the purpose unambiguous.

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?

The description explicitly provides guidance: this tool is for frequency analysis only, and if buy/sell sentiment is needed, it directs users to use analyze_form4_transactions. This clearly tells when to use this tool versus an alternative.

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