Skip to main content
Glama

get_form144_notices

Read-onlyIdempotent

Get SEC Form 144 filings — notices of proposed sale of restricted/controlled securities by insiders. Filed before selling, these signal upcoming insider sales. Complements Form 4 (post-trade) with pre-trade intent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax notices to return
tickerNoFilter by stock ticker (e.g. 'AAPL')
insider_cikNoFilter by insider's CIK number

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsYes
pagingYesPaging state reconciled from ko.io meta.total_count and meta.softwall
filtersYes
plan_limitYesThe Free/keyless plan limits ko.io applied to this answer (null for paid callers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "filters": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "insider_cik": {
      +          "$ref": "#/properties/filters/properties/ticker"
      +        },
      +        "ticker": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "ticker",
      +        "insider_cik"
      +      ],
      +      "type": "object"
      +    },
      +    "paging": {
      +      "additionalProperties": false,
      +      "description": "Paging state reconciled from ko.io meta.total_count and meta.softwall",
      +      "properties": {
      +        "continuation": {
      +          "description": "SIGNIN_REQUIRED = page>1 needs a (free) ko.io API key",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "has_more": {
      +          "description": "null = a full page came back and more MAY exist",
      +          "type": [
      +            "boolean",
      +            "null"
      +          ]
      +        },
      +        "next_page": {
      +          "anyOf": [
      +            {
      +              "$ref": "#/properties/paging/properties/total_count/anyOf/0"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "Next page THIS caller can open; null when there is none (or sign-in is required)"
      +        },
      +        "page": {
      +          "type": "integer"
      +        },
      +        "per_page": {
      +          "type": "integer"
      +        },
      +        "plan_row_cap": {
      +          "anyOf": [
      +            {
      +              "$ref": "#/properties/paging/properties/total_count/anyOf/0"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "Row cap the caller's plan applied to this page, if any"
      +        },
      +        "returned": {
      +          "type": "integer"
      +        },
      +        "total_count": {
      +          "anyOf": [
      +            {
      +              "type": "integer"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "Total rows matching the request, when ko.io reported it"
      +        },
      +        "truncated_by_plan": {
      +          "description": "True when the plan's row cap withheld rows from this page",
      +          "type": "boolean"
      +        }
      +      },
      +      "required": [
      +        "page",
      +        "per_page",
      +        "returned",
      +        "total_count",
      +        "has_more",
      +        "next_page",
      +        "continuation",
      +        "plan_row_cap",
      +        "truncated_by_plan"
      +      ],
      +      "type": "object"
      +    },
      +    "plan_limit": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": false,
      +          "properties": {
      +            "continuation": {
      +              "$ref": "#/properties/filters/properties/ticker"
      +            },
      +            "date_basis": {
      +              "$ref": "#/properties/filters/properties/ticker"
      +            },
      +            "effective_period": {
      +              "$ref": "#/properties/filters/properties/ticker"
      +            },
      +            "policy_version": {
      +              "$ref": "#/properties/filters/properties/ticker"
      +            },
      +            "row_cap": {
      +              "anyOf": [
      +                {
      +                  "$ref": "#/properties/paging/properties/total_count/anyOf/0"
      +                },
      +                {
      +                  "type": "null"
      +                }
      +              ]
      +            },
      +            "truncated": {
      +              "type": [
      +                "boolean",
      +                "null"
      +              ]
      +            },
      +            "window_end": {
      +              "$ref": "#/properties/filters/properties/ticker"
      +            },
      +            "window_start": {
      +              "$ref": "#/properties/filters/properties/ticker"
      +            }
      +          },
      +          "required": [
      +            "policy_version",
      +            "window_start",
      +            "window_end",
      +            "effective_period",
      +            "date_basis",
      +            "row_cap",
      +            "truncated",
      +            "continuation"
      +          ],
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "The Free/keyless plan limits ko.io applied to this answer (null for paid callers)"
      +    },
      +    "rows": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "accession_no": {
      +            "$ref": "#/properties/filters/properties/ticker"
      +          },
      +          "aggregate_market_value": {
      +            "anyOf": [
      +              {
      +                "$ref": "#/properties/rows/items/properties/units_to_sell/anyOf/0"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ],
      +            "description": "Exact decimal string as served by ko.io (not rounded); null = unknown"
      +          },
      +          "approx_sale_date": {
      +            "$ref": "#/properties/filters/properties/ticker"
      +          },
      +          "broker_name": {
      +            "$ref": "#/properties/filters/properties/ticker"
      +          },
      +          "filed_date": {
      +            "$ref": "#/properties/filters/properties/ticker"
      +          },
      +          "has_10b5_1_plan": {
      +            "type": [
      +              "boolean",
      +              "null"
      +            ]
      +          },
      +          "issuer_cik": {
      +            "$ref": "#/properties/filters/properties/ticker"
      +          },
      +          "issuer_name": {
      +            "$ref": "#/properties/filters/properties/ticker"
      +          },
      +          "issuer_ticker": {
      +            "$ref": "#/properties/filters/properties/ticker"
      +          },
      +          "relationship": {
      +            "$ref": "#/properties/filters/properties/ticker"
      +          },
      +          "securities_class": {
      +            "$ref": "#/properties/filters/properties/ticker"
      +          },
      +          "seller_name": {
      +            "$ref": "#/properties/filters/properties/ticker"
      +          },
      +          "units_to_sell": {
      +            "anyOf": [
      +              {
      +                "pattern": "^-?\\d+(\\.\\d+)?([eE][-+]?\\d+)?$",
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ],
      +            "description": "Units the filer NOTIFIED an intent to sell -- not a completed sale"
      +          }
      +        },
      +        "required": [
      +          "accession_no",
      +          "filed_date",
      +          "issuer_ticker",
      +          "issuer_name",
      +          "issuer_cik",
      +          "seller_name",
      +          "relationship",
      +          "securities_class",
      +          "units_to_sell",
      +          "aggregate_market_value",
      +          "approx_sale_date",
      +          "broker_name",
      +          "has_10b5_1_plan"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "filters",
      +    "rows",
      +    "paging",
      +    "plan_limit"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety and idempotency. The description adds semantic context (pre-trade intent) but no additional behavioral traits such as rate limits, pagination, or auth requirements. Since the annotations carry the main behavioral burden, the description does not contradict them and provides marginal added value, warranting a 3.

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?

The description is two sentences long, front-loading the core action ('Get SEC Form 144 filings') and then providing essential context. It is efficient with no wasted words, though it could be even more concise by trimming the redundant explanation of what Form 144 is.

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

Completeness4/5

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

For a simple read-only tool with three optional parameters and an output schema, the description explains the purpose and the nature of the data (pre-trade insider sales) adequately. It does not mention any edge cases or limitations (e.g., date ranges, coverage), but given the output schema and annotations, an agent can likely invoke it correctly. Slightly more detail on return behavior would improve it, but it is not essential.

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

Parameters3/5

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

Schema description coverage is 100%, with each parameter (limit, ticker, insider_cik) having a clear description. The tool description does not add any extra meaning or clarify syntax beyond what the schema already provides. Baseline of 3 applies because the schema fully documents parameters.

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?

Description clearly states the verb 'Get' and resource 'SEC Form 144 filings', then explains what these filings are (notices of proposed sale of restricted/controlled securities by insiders). It adds context that they signal upcoming insider sales, which distinguishes it from general insider-trade tools, though it doesn't explicitly name a sibling alternative. The purpose is unambiguous.

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?

The description implies a use case ('signal upcoming insider sales') and contrasts with Form 4 (post-trade vs pre-trade intent), giving some situational guidance. However, it does not explicitly state when to choose this tool over siblings like get_insider_trades or sec_list_filings, nor does it mention any exclusions or prerequisites. Guidance is present but not fully explicit.

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.