Skip to main content
Glama
SiftingIO

siftingio-mcp

Official

Insider transactions

stocks_insiders
Read-only

List a company's insider transactions from SEC Form 3/4/5 filings, most recent first. Includes officers, directors, and 10% owners.

Instructions

List a company's insider transactions from SEC Form 3/4/5 filings (officers, directors, 10% owners), most recent first. Paginate with cursor/limit (default 10, max 25), or set max_items to auto-collect across pages. For large outside stakeholders (13D/13G) use stocks_ownership.

Input Schema

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

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

Annotations already provide readOnlyHint and openWorldHint. Description adds important behavioral details: ordering (most recent first), pagination mechanisms (cursor/limit, max_items for auto-paginate). Does not mention rate limits or other constraints.

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, front-loaded with purpose, then pagination and alternative tool. Every sentence is informative with no redundancy.

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?

No output schema exists, so description should provide some detail about return structure (e.g., fields like filing date, transaction type). The description only mentions ordering and pagination, missing what the response contains.

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 coverage is 100%, but description adds context: limit default 10 max 25, max_items auto-collects (ignores cursor), cursor is opaque. Adds value beyond schema descriptions.

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?

Explicitly states it lists insider transactions from SEC Form 3/4/5 filings, specifies officers/directors/10% owners, and distinguishes from stocks_ownership for 13D/13G.

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?

Clearly says when to use this tool (for insider transactions) and when to use alternative (stocks_ownership for 13D/13G), plus explains pagination with cursor/limit and 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