Skip to main content
Glama
Sign In
Financial Modeling Prep MCP Server

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

searchInsiderTrades

Read-onlyIdempotent

Search insider trading activity by company, symbol, or CIK to find specific trades by executives and directors. Filter by transaction type and paginate results.

Instructions

Search insider trading activity by company or symbol using the Search Insider Trades API. Find specific trades made by corporate insiders, including executives and directors.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 0)
limitNoLimit on number of results (default: 100, max: 100)
symbolNoStock symbol
companyCikNoCompany CIK number
reportingCikNoReporting CIK number
transactionTypeNoTransaction type (e.g., S-Sale)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.9.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds only that results cover insiders including executives and directors; it says nothing about result volume, pagination limits, or how the optional filters combine — though the schema's 100% coverage partially compensates.

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?

Two short sentences, front-loaded with the core action. The second sentence partially restates the first ('Search insider trading activity' / 'Find specific trades made by corporate insiders') but adds the executive/director detail, so waste is minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-optional-filter search tool with no output schema and no annotations gap, the definition is adequate but thin: it never indicates what a result contains (trade rows) or how many to expect, and it omits any routing hint to the reporting-name or latest-trades siblings. Nothing an agent needs to call it is missing, but differentiation is.

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?

All six parameters are fully described in the schema (page, limit, symbol, companyCik, reportingCik, transactionType), so the baseline is 3 per the coverage rule. The description's mention of 'by company or symbol' loosely maps to symbol/companyCik but adds no meaning about reportingCik, transactionType, or filter combination behavior.

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 verb+resource ('Search insider trading activity') and scopes it to 'by company or symbol', plus clarifies the data covers executives and directors. It does not distinguish this from close siblings such as getLatestInsiderTrading or searchInsiderTradesByReportingName, which keeps it from a 5.

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

Usage Guidelines3/5

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

The phrase 'by company or symbol' implies this is the targeted filter-based search (versus the 'latest' feed sibling), which is useful implied usage guidance. However, there is no explicit when-to-use/when-not statement and no named alternative, notably searchInsiderTradesByReportingName which overlaps in scope.

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

Deploy Server

Other Tools