Skip to main content
Glama

equibles

by io.github.daniel3303

Proposed Insider Sales (Form 144)

GetForm144ProposedSales
Read-only

Get recent proposed insider sales for a stock from SEC Form 144 notices. Each Form 144 is an affiliate's declaration of intent to sell restricted or control securities, showing the seller, their relationship to the company, the number of shares and aggregate market value to be sold, the proposed sale as a share of the issuer's current shares outstanding, the approximate sale date, the broker, and the filer's remarks (including any stated 10b5-1 plan). Results are the most recent notices first and a note flags when more exist than were returned; use fromDate/toDate to scope a period (heavy 10b5-1 filers can flood the recency window with small daily notices). A proposal may never execute; a completed sale may later appear on Form 4 or 5 only when it is reportable there.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoNumber of matching notices to skip before returning rows (default: 0)
tickerYesCompany ticker symbol (e.g., AAPL, MSFT)
toDateNoOptional latest filing date to include, ISO format yyyy-MM-dd (e.g., 2025-12-31)
fromDateNoOptional earliest filing date to include, ISO format yyyy-MM-dd (e.g., 2025-01-01)
maxResultsNoMaximum number of notices to return (default: 50, max: 500; values outside 1-500 are clamped)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Number of matching notices to skip before returning rows (default: 0)",
+  "type": "integer"
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

The annotations only declare the tool read-only and non-destructive. The description adds valuable behavioral context: results are sorted with the most recent notices first, a note flags when more results exist than returned, heavy 10b5-1 filers can flood the recency window, and a Form 144 proposal may never execute. These details go well beyond the structured annotations.

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 dense but not padded; every sentence contributes value: purpose, returned fields, sort order, overflow behavior, date-scoping rationale, and legal caveats. It is front-loaded with the core capability and then fills in the nuances an agent would need to interpret results correctly.

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

Completeness5/5

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

Given that there is no output schema, the description compensates well by enumerating the key returned fields: seller, relationship, shares, aggregate market value, percent of shares outstanding, approximate sale date, broker, and remarks/10b5-1 plans. It also covers ordering, overflow, date filtering, and the caveat that proposals may never execute. Nothing essential for correct invocation or interpretation is missing.

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?

The input schema documents all 5 parameters with descriptions, so the baseline is 3. The description adds extra meaning by explaining why fromDate/toDate matter — heavy 10b5-1 filers can flood the recency window — and noting that an overflow flag appears when more results exist than were returned. This goes slightly beyond the schema's basic 'filter' language.

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 begins with 'Get recent proposed insider sales for a stock from SEC Form 144 notices,' a specific verb and resource. It makes clear these are declarations of intent, not completed trades, which distinguishes it from actual insider transaction tools like GetInsiderTransactions. The subsequent Form 4/5 note further reinforces the precise scope.

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

Usage Guidelines4/5

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

It gives concrete guidance to use fromDate/toDate to scope the period because heavy 10b5-1 filers can flood the recency window with small notices. It also warns that a proposal may never execute and that completed sales may only show up on Form 4 or 5 when reportable, which helps agents know when not to over-interpret results. However, it does not explicitly name a sibling tool as the alternative for executed sales, so it stops short of a 5.

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

All equibles toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, with detailed descriptions that cross-reference related alternatives. A few near-duplicate names could cause misselection, notably SearchDocument versus SearchDocuments and GetCftcPositioning versus GetLatestCftcPositioning.

Naming Consistency5/5

Tool names consistently follow a VerbNoun camelCase pattern: Get for retrievals, Search for discovery, List/Read for document access, and Add/Close/Remove/Update/Watch/Create/Delete for portfolio mutations. Despite the large count, there is no mixing of naming conventions or unpredictable verb styles.

Tool Count1/5

108 tools is an extreme surface area, far beyond the 3-15 well-scoped range and well past the 25+ threshold. Even for a broad financial data platform, this creates a heavy selection burden and substantial context overhead for agents.

Completeness4/5

The server covers an unusually wide domain: prices, fundamentals, SEC filings, options, insider activity, 13F holdings, short interest, macro data, funds, IPOs, and full portfolio lifecycle management. Notable gaps remain, such as a basic company profile/ticker-resolution tool, dividend history, and analyst estimates, so it is not a perfect 5.

Resources