Skip to main content
Glama

Arkanum Data: SEC insider trades

Large insider sales

large_insider_sales
Read-only

Large insider sales not made under a pre-set 10b5-1 plan, biggest first, with the share of the insider's holding each sold. 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": "large_insider_sales"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
tickerNo
min_valueNo
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 establish a safe read (readOnlyHint true, openWorldHint false), so the bar is lower. The description adds real behavioral context beyond them: a hard 30-day window, exclusion of 10b5-1 plan sales, descending-value ordering, and the returned 'share of holding sold' field. It does not explain pagination or what happens when the window and filed_from conflict, which keeps it from a 5.

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?

Three terse sentences, front-loaded with the defining filter (excluding 10b5-1 plans) and with zero filler. The telegraphic fragments 'Last 30 days' and 'Hobby and Pro' are efficient but slightly under-explained, which costs a point on clarity rather than length.

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?

With four parameters, no output schema, and sparse annotations, the description should carry more weight than it does. It conveys the result concept well but leaves the filtering behavior of min_value, ticker, and filed_from undefined and never clarifies the plan-tier restriction. Adequate to attempt a call, but not enough to call it confidently.

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 description coverage is only 25% (only filed_from is documented), so the description must compensate and does not. limit, ticker, and especially min_value (defaulting to 1,000,000) are never explained, and the 'Last 30 days' phrase ambiguously overlaps the filed_from parameter without saying whether it overrides the default window. This leaves the majority of the parameters' meaning unstated.

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?

The description names a precise resource and narrows it with meaningful qualifiers: large insider sales, excluding pre-set 10b5-1 plans, sorted biggest first, with the insider's sold share of holdings included. That is specific enough to separate it from buy-oriented or unfiltered siblings such as unusual_insider_buys and latest_insider_trades. It stops short of naming an alternative, so it lacks full explicit sibling differentiation.

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?

Usage is only implied through the fixed 'Last 30 days' window and the 'Hobby and Pro' plan note, which signals tier availability but never explains it. There is no statement of when to prefer this over latest_insider_trades or search_insider_trades, and no exclusions. An agent can infer the use case from the filters but must guess about alternatives.

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