Skip to main content
Glama
theodor90

form4api-mcp

by theodor90

get_insider_leaderboard

Read-only

Rank insiders by historical buy performance using hit rate or average return over a chosen horizon. Identify top-performing insiders based on scored open-market buys.

Instructions

Ranked leaderboard of insiders by buy track-record (Business plan+). Returns the top insiders ranked by historical buy performance — same scored-buy methodology as GET /v1/insiders/{cik}/scorecard, applied across the whole corpus rather than one insider. Use this to discover which insiders have the best track record; use the per-insider scorecard once you have a specific CIK. Scores use absolute return (NOT market-adjusted) — a hit is a scored buy with a positive 3m (or 6m) return anchored at the filing-date close. Only discretionary open-market buys (P-code, not 10b5-1, not derivative) with a matured return are counted. Insiders with fewer than min_trades (floor 5) scored buys are excluded. Requires Business plan or higher (402 PLAN_REQUIRED on Free/Starter/Pro). Results are cached for 1 hour per unique parameter combination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of insiders to return. Defaults to 25, maximum 100.
orderNo"hit_rate" (% of scored buys with a positive return) or "avg_return" (mean scored return). Defaults to "hit_rate".
horizonNo"3m" or "6m" — the post-trade return horizon to score and rank by. Defaults to "3m".
min_tradesNoMinimum number of scored buys an insider must have to be ranked. Defaults to 5; values below 5 are silently raised to 5 (the scorecard sample-sufficiency floor).
Behavior5/5

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

Discloses key behavioral traits beyond annotations: uses absolute return (not market-adjusted), only discretionary open-market buys, excludes non-10b5-1 buys, min_trades floor of 5, caching for 1 hour, and plan requirement. These details are not in the readOnlyHint or openWorldHint annotations.

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?

Well-structured with front-loaded purpose. Each sentence adds value, but the description is relatively long. For the complexity, it's acceptable; minor room for tightening.

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?

Covers return values implicitly, explains methodology, plan requirement, and caching. Without an output schema, it provides adequate context for an agent to understand what is returned and how it is computed.

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%, so baseline is 3. The description adds value by explaining the min_trades floor (silently raised to 5) and referencing the scoring methodology. However, it does not enumerate each parameter's details beyond what the schema provides.

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 the tool returns a ranked leaderboard of insiders by buy track record, distinguishing it from the per-insider scorecard sibling tool. It uses specific language like 'ranked leaderboard' and 'scored-buy methodology' to convey purpose.

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?

Explicitly says 'Use this to discover which insiders have the best track record; use the per-insider scorecard once you have a specific CIK.' It also notes the Business plan requirement and caching behavior, guiding appropriate usage.

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/theodor90/form4api-mcp'

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