Skip to main content
Glama
theodor90

form4api-mcp

by theodor90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_signals

Read-only

Cluster buy/sell signals — multiple insiders at the same company trading in the same direction within a short window, a stronger conviction signal than any single trade. Excludes 10b5-1 plan trades automatically by construction.

Instructions

Cluster buy/sell signals — multiple insiders at the same company trading in the same direction within a short window, a stronger conviction signal than any single trade. Excludes 10b5-1 plan trades automatically by construction. Returns signal type, detection date, buyer/seller counts, total $ value, and the underlying transactions. Use this to FIND which companies have signals; when the user already names a company and asks WHY its signal fired or which insiders were in the cluster, call explain_signal with that ticker directly instead. Use get_transactions instead for raw, unaggregated trade search. Requires Business plan (a 402 upgrade_required response is returned otherwise). Paginated, max 50/page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number. Defaults to 1.
tickerNoFilter to a specific company ticker, case-insensitive, e.g. NVDA. Omit for a market-wide scan across all companies.
per_pageNoResults per page. Defaults to 20, maximum 50.
cluster_buyNoIf true, return only ClusterBuy signals (multiple insiders buying together). Omit both cluster_buy and cluster_sell to return signals of either type.
cluster_sellNoIf true, return only ClusterSell signals (multiple insiders selling together). Omit both cluster_buy and cluster_sell to return signals of either type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / cluster_buy / description
      Previous value: -"Only return cluster buy signals"New value: +"If true, return only ClusterBuy signals (multiple insiders buying together). Omit both cluster_buy and cluster_sell to return signals of either type."
    • changedInput schema / properties / cluster_sell / description
      Previous value: -"Only return cluster sell signals"New value: +"If true, return only ClusterSell signals (multiple insiders selling together). Omit both cluster_buy and cluster_sell to return signals of either type."
    • changedInput schema / properties / page / description
      Previous value: -"Page number"New value: +"1-based page number. Defaults to 1."
    • changedInput schema / properties / per_page / description
      Previous value: -"Results per page (max 50)"New value: +"Results per page. Defaults to 20, maximum 50."
    • changedInput schema / properties / ticker / description
      Previous value: -"Filter to a specific company ticker"New value: +"Filter to a specific company ticker, case-insensitive, e.g. NVDA. Omit for a market-wide scan across all companies."
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses that 10b5-1 plan trades are excluded by construction (a non-obvious data-semantics fact), that a Business plan is required with a 402 upgrade_required response otherwise, and that results are paginated at max 50/page. These are exactly the behavioral facts annotations cannot carry.

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?

Front-loads the concept definition, then routing, then constraints. No sentence is filler: even the return-field list earns its place because no output schema exists.

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?

With no output schema, the description names the returned fields (signal type, detection date, buyer/seller counts, total value, underlying transactions) and covers auth, pagination, and result semantics. Nothing needed to call it correctly is missing.

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%, so page, per_page, ticker, cluster_buy, and cluster_sell are already fully documented, including the omit-both-to-get-either rule. The description adds pagination context but no parameter syntax or format detail beyond the schema, so the baseline 3 applies.

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+resource and defines the domain concept ('multiple insiders at the same company trading in the same direction within a short window'), then distinguishes the tool from both explain_signal and get_transactions by name. An agent can identify this as the market-wide signal-discovery tool without opening any schema.

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

Usage Guidelines5/5

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

Explicit routing: 'Use this to FIND which companies have signals', call explain_signal when a company is already named and the user asks WHY, and use get_transactions for raw unaggregated search. Both alternatives and the selecting conditions are stated.

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

Deploy Server

Other Tools