Skip to main content
Glama
SiftingIO

siftingio-mcp

Official

Insider transactions

stocks_insiders
Read-only

Retrieve insider transaction data from SEC Form 3/4/5 filings for US equities, including transaction details and filing dates.

Instructions

Form 3/4/5 insider transactions (limit default 10, max 25).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesUS equity ticker, e.g. AAPL.
cursorNoOpaque cursor from a previous response's meta.next_cursor.
limitNoPage size (endpoint-specific default and max).
max_itemsNoIf set, auto-paginate across pages and return up to this many items (ignores cursor).
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint. Description adds limit defaults and max (10/25), but does not disclose pagination behavior, error handling, or data recency. Acceptable given annotation coverage.

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?

Single sentence, front-loads the core purpose (Form 3/4/5 insider transactions), then specifies constraints. No extraneous words.

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

Completeness2/5

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

Very brief for a 4-parameter tool with no output schema. Lacks explanation of cursor usage, auto-pagination via max_items, response format, or how to interpret insider transaction data. Expects agent to infer too much.

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?

Schema descriptions cover all 4 parameters (100%), but description adds specific default (10) and max (25) for limit, plus context 'Form 3/4/5' not in schema. This enriches parameter understanding beyond schema alone.

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?

Clearly states it provides Form 3/4/5 insider transactions for stocks, with specific limit defaults. Distinguishes from siblings like 'stocks_ownership' or 'stocks_compensation' by focusing on insider transaction filings.

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 related siblings. Does not indicate alternative tools for similar data (e.g., ownership, compensation) or when to use cursor vs. max_items.

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/SiftingIO/siftingio-mcp'

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