Skip to main content
Glama

Arkanum Data: SEC insider trades

Unusual insider buys

unusual_insider_buys
Read-only

Insider purchases ranked by Insider Activity Score (how out of the ordinary each buy is: who bought, how much their stake grew, first buy in years, several insiders buying), highest first. Last 30 days. Hobby and Pro.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "unusual_insider_buys"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
tickerNo
min_scoreNo
filed_fromNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavior beyond that: results are sorted descending by a composite score, the window is fixed at 30 days, the score's drivers are enumerated, and tier availability is stated. It does not describe pagination or the shape of each row.

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?

Front-loads the operation and ranking order, then unpacks the score definition and scope in two short fragments. Nearly every clause earns its place; the tier note is the only part that could be trimmed for some audiences.

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?

A read-only query tool with no output schema needs to convey what comes back and under what filter, and this description covers the ranking, the score basis, and the time window. It leaves three of four parameters entirely unexplained, which is a real gap for an agent trying to tune results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25% — only filed_from carries an inline description, and only as a date format. The description never mentions limit, ticker, or min_score, and provides no syntax or default behavior for any of them. Explaining the Insider Activity Score does implicitly motivate min_score, but that is inference rather than stated mapping.

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?

Names a specific verb+resource: insider purchases ranked by Insider Activity Score, highest first, over the last 30 days. The parenthetical explanation of what the score measures makes the tool's output substantive rather than generic. It stops short of distinguishing itself from siblings like insider_clusters or latest_insider_trades, so not a 5.

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?

"Last 30 days" establishes the scope within which this tool applies, and "Hobby and Pro" signals plan-tier availability. There is no explicit when-to-use-versus-alternative guidance and no statement of when this ranked view is preferable to the other insider tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources