Skip to main content
Glama

Otto Form 144 filings

otto_proposed_insider_sales
Read-onlyIdempotent

Read the SEC Form 144 notices of proposed insider sales for a US ticker, which are filed before the Form 4 that reports an executed trade: who intends to sell, the units, the filer’s own market-value estimate, the broker, the approximate sale date and any Rule 10b5-1 plan dates. Up to the latest 20 notices in a 90-day lookback. The list may be empty when no notices were filed in the window; that answer is charged. A notice is not a completed trade and may never be executed. Not investment advice. Hosted access: the first eligible cached intelligence result is free; otherwise calls cost $0.005 USDC through x402.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "otto_proposed_insider_sales"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesUS-listed stock ticker, for example NVDA, AAPL, or JPM.
x_paymentNoSigned x402 payment payload. Omit it to receive the machine-actionable payment challenge, then retry with the signed payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety bar is low; the description still adds substantial unique context: the 20-record cap, the 90-day window, that an empty answer is still billable, and the paid-access model with a free cached result. It also warns that a notice may never be executed, which is a genuine domain caveat absent from any structured field.

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 defining sentence is front-loaded with the returned fields enumerated in a single dense clause, and the caveats follow in short sentences. It is on the long side, with the 'Not investment advice' and pricing lines adding bulk, but each sentence carries distinct information.

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?

There is no output schema, so the description must describe returns, and it does so by enumerating the fields a notice carries (filer intent, units, market-value estimate, broker, approximate sale date, 10b5-1 plan dates). Combined with the window and cap limits, an agent has enough to call this and interpret the result without further documentation.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds value by characterizing the ticker as a US-listed equity and by explaining the hosted/x402 payment context that gives the x_payment parameter its purpose. It does not restate the ticker's regex or format, which the schema already covers.

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?

States a specific verb and resource ('Read the SEC Form 144 notices of proposed insider sales') scoped to a US ticker, and immediately positions the resource relative to the Form 4 executed-trade filing. That framing lets an agent separate this from the executed-insider-trades sibling without opening either schema.

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?

Gives the operational envelope (latest 20 notices, 90-day lookback) and the key interpretive rule that a notice is not a completed trade and the list may be empty, which tells the agent when the result is meaningful. It stops short of naming a specific alternative tool to call for executed trades, leaving that inference to the Form 4 contrast.

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