Skip to main content
Glama

SEC Form 144 notices of proposed sale

planned_insider_sales

Fetch Form 144 filings by ticker and lookback days to see an affiliate's planned sale of restricted or control stock, including seller, shares, market value, and planned date.

Instructions

Form 144 notices: an affiliate's planned sale of restricted or control stock (seller, shares, approximate market value, planned date), filed before the trade.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNo
symbolNoUS ticker symbol, e.g. GME. Class shares as on the SEC list, e.g. BRK-B.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the nature of Form 144 filings, but does not state whether the operation is read-only, what permissions are needed, whether data is delayed, or any other behavioral trait beyond the basic resource definition.

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?

The description is a single, front-loaded sentence with no filler. It packs the resource type, subject, key fields, and timing context efficiently.

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

Completeness2/5

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

Given no annotations, no output schema, and only 50% schema description coverage, the description is incomplete. It does not explain how to use the input parameters, what the call returns structurally, or any behavioral constraints needed to invoke the tool correctly.

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

Parameters1/5

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

The description adds no meaning for the two input parameters. The symbol parameter is already documented in the schema, and the days parameter has no schema description and is not addressed by the description at all. The parenthetical list refers to notice contents, not input controls.

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 clearly states the resource: SEC Form 144 notices of planned insider sales by affiliates. It specifies the subject matter and distinguishes the data from completed insider trades, though it does not explicitly name the sibling tool insider_trades as an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus alternatives, nor are any prerequisites or exclusions stated. The phrase 'filed before the trade' implies timing but does not tell an agent when to choose this tool over insider_trades or other sibling tools.

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