Skip to main content
Glama
imbenrabi

Financial Modeling Prep MCP Server

getLatestInsiderTrading

Read-onlyIdempotent

Retrieve insider trading transactions for any date, showing which company insiders bought or sold stocks. Analyze transaction details with pagination and result limits.

Instructions

Access the latest insider trading activity using the Latest Insider Trading API. Track which company insiders are buying or selling stocks and analyze their transactions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate of insider trades (YYYY-MM-DD)
pageNoPage number (default: 0)
limitNoLimit on number of results (default: 100, max: 100)
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description is consistent with read-only behavior. However, the description adds no additional behavioral details (e.g., pagination defaults, date range handling) beyond what annotations imply, so it contributes little extra transparency.

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?

Two sentences, succinctly front-loaded with the purpose. Every sentence is informative and non-redundant. Excellent conciseness.

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?

With no output schema, the description could hint at the response structure (e.g., fields like transaction type, insider name, volume). The tool has many siblings; the description is adequate but not rich enough for an agent to fully understand what data is returned.

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?

Input schema covers 100% of parameters with descriptions, so the baseline is 3. The description does not add extra meaning or context for the parameters (date, page, limit) beyond 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 uses a specific verb ('Access') and clearly states the resource ('latest insider trading activity'). It distinguishes this tool from siblings like searchInsiderTrades or getInsiderTradeStatistics by emphasizing 'latest' and 'track which company insiders are buying or selling'.

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 description implies when to use (to get latest insider trades) but does not provide explicit guidance on when not to use it or mention alternatives. Given the many insider-trading sibling tools, the absence of exclusion criteria or comparative context is a gap.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/imbenrabi/Financial-Modeling-Prep-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server