Skip to main content
Glama

get_insider_trades

Retrieve insider buying and selling activity and summary statistics for any stock by symbol.

Instructions

Get insider buying/selling activity and summary statistics for a stock.

Fetches recent insider transactions and aggregate insider trading stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax trade rows to return in summary mode (default: 20).
formatNoOutput format: - "summary": Normalized recent trades and key stats - "full": Raw endpoint payloadssummary
symbolYesStock symbol (required, e.g., "AAPL").
use_cacheNoUse cached data when available (default: True).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations provided, the description carries full burden. It mentions fetching recent transactions and aggregate stats but does not clarify recency limits, caching behavior, or potential side effects beyond what is in the schema.

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 concise with two sentences. The first sentence clearly states purpose, though there is slight redundancy between the two sentences.

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?

Given the tool has 4 parameters and an output schema, the description covers the core functionality. However, it lacks context on when to use different format options or how caching works, making it minimally adequate.

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 coverage is 100%, and each parameter has a description in the schema. The tool description does not add extra meaning beyond the schema, so baseline 3 is appropriate.

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 it retrieves insider buying/selling activity and summary statistics for a stock, specifying the resource and action. It distinguishes itself from sibling tools like get_institutional_ownership by focusing specifically on insider trades.

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 on when to use this tool versus alternatives such as get_institutional_ownership or fmp_fetch. There is no mention of prerequisites, optimal contexts, or exclusions.

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/henrysouchien/fmp-mcp'

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