Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sec_insider

Fetch a company's recent insider transactions from SEC Forms 3/4/5 using its CIK or ticker. Get owner, role, security, shares, and price details.

Instructions

Insider transactions (Forms 3/4/5). Returns a company's recent insider transactions from Form 3/4/5 ownership filings (owner, role, security, shares, price). Provide cik or ticker.

Input Schema

NameRequiredDescriptionDefault
cikNoSEC CIK (numeric or zero-padded)
limitNoMax transactions, default 10, max 30
tickerNoTicker symbol (alternative to cik)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the returned fields (owner, role, security, shares, price) and implies a read-only operation via 'Returns', which is genuinely useful. It does not disclose the 'recent' time window, pagination/limit behavior, or any auth or rate-limit constraints, leaving notable gaps.

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 sentences, front-loaded with the operation and followed by the return fields and required identifiers. There is mild redundancy, since 'Insider transactions (Forms 3/4/5)' and 'Form 3/4/5 ownership filings' restate the same thing, but nothing is wasted overall.

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

Completeness4/5

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

For a simple three-parameter read tool with no output schema, the description covers the operation, the source filings, and the return fields, which is most of what an agent needs. Missing only the recency window and the limit's default/max, the latter of which the schema already supplies.

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 description coverage is 100%, so the schema already fully documents cik, ticker, and limit, making 3 the baseline. The description reinforces the cik-or-ticker alternative but adds no syntax, format, or precedence detail beyond what the schema states. It neither under- nor over-delivers on parameter meaning.

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?

States a specific verb and resource: returns a company's recent insider transactions from Form 3/4/5 ownership filings. The filing-type scoping is precise and distinguishes it from generic filing tools. However, it never names or contrasts itself against close siblings like sec_institutional_holdings or datasets_sec_companies_insider, so the reader must infer the boundary.

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 final sentence 'Provide cik or ticker' tells the agent which inputs to supply, which is minimal but real usage guidance. There is no explicit when-to-use vs alternative, no statement of prerequisites, and no note about which identifier is preferred when both are available. Adequate but with clear gaps.

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