Skip to main content
Glama

Arkanum Data: SEC insider trades

Planned insider sales (Form 144)

form_144_notices
Read-only

The latest Form 144 notices: insiders announcing a planned sale, usually on or before the day they sell, with shares, the filer's stated market value, the expected sale date and their sales in the past 3 months. From the last seven days, newest first. 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": "form_144_notices"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
tickerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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, and the description usefully adds behavior beyond that: a hard seven-day recency window, newest-first ordering, and the 'Pro' tag signalling a paid/entitlement requirement. It does not mention pagination behavior or the cost of the limit ceiling, but the freshness and ordering constraints are the operationally important disclosures.

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?

A single dense sentence that front-loads the resource and follows with scope and return fields; the trailing 'Pro.' efficiently flags tier without padding. Nothing is wasted or buried.

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 no output schema, the description does a good job enumerating returned fields, and the seven-day window defines the result set. However, for a two-parameter tool with zero schema coverage, leaving both limit and ticker unexplained is a real completeness gap an agent would hit when trying to narrow results to one company.

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 0% for both limit (default 25, max 50) and ticker, so the description carries the full burden — yet it never mentions either parameter. In particular, the existence of ticker-based filtering is undiscoverable from the description, which discusses only returned fields.

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 gives a specific verb and resource — Form 144 notices of insiders' planned sales — and enumerates the payload (shares, stated market value, expected sale date, trailing 3-month sales history), so an agent knows exactly what it returns. It does not distinguish itself from siblings such as latest_insider_trades or large_insider_sales, so an agent must still 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?

Usage is only implied through scope statements: 'the latest' and 'from the last seven days, newest first' tell the agent this is a recent-window feed, not a historical search. There is no explicit statement of when to choose this over the many insider-related siblings, and no exclusion of past-date lookups.

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