Skip to main content
Glama
clousai

Clous MCP server

Official
by clousai

search_form144

Search SEC Form 144 proposed-sale notices to track insider intent to sell restricted or control stock.

Instructions

Search Form 144 proposed-sale notices (insiders' intent to sell restricted/control stock).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size, 1–100 (default 25).
cursorNoPagination cursor from a prior page's page.next_cursor.
issuer_cikNo
min_sharesNo
sale_date_toNo
sale_date_fromNo
class_of_securitiesNo
min_market_value_usdNo
broker_normalized_nameNo
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'search' which implies a read-only operation, but does not disclose pagination, defaults, filtering behavior, or response format. This is significantly minimal for a tool with nine parameters.

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 sentence with no filler. It is front-loaded with the action, and the parenthetical adds useful context. Every word earns its place.

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

Completeness1/5

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

Given the complexity of nine filter parameters and no output schema or annotations, a one-line description is grossly insufficient. It does not explain the intended use case, filter combinations, pagination protocol, or what constitutes a Form 144 notice. The tool is highly under-specified for an AI agent to invoke reliably.

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?

Schema coverage is only 22%, and the description mentions zero parameters. It does not clarify the meaning or use of issuer_cik, min_shares, sale_date_from/to, class_of_securities, or other filters. The description adds no value beyond the schema, which itself has sparse descriptions.

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 clearly states the tool searches Form 144 proposed-sale notices, with a parenthetical explaining it covers insiders' intent to sell restricted/control stock. This uses a specific verb + resource and differentiates it from sibling tools like search_insider_transactions or search_filings.

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?

No guidance is provided on when to use this tool versus alternatives. The description only implies usage by naming Form 144, but it does not mention scenarios, exclusions, or how it differs from related search tools like search_insider_transactions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/clousai/Mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server