Skip to main content
Glama

Trading Signals Toolkit

SEC Insider Cluster Buys (market-wide)

insider_clusters
Read-only

Listed tickers where several distinct insiders made open-market purchases (Form 4 code P) in the last N days, with buyers, roles, totals and VWAP. From SEC EDGAR. Read-only, never places orders. Informational only, not investment advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "insider_clusters"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLookback by filing date (1-14, default 7)
minBuyersNoMinimum distinct insider buyers (2-10, default 3)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, openWorldHint and idempotentHint, so the safety bar is low; the description still adds real context by naming the data source (SEC EDGAR), restricting scope to Form 4 code P open-market purchases, and enumerating returned fields (buyers, roles, totals, VWAP). The 'never places orders' and 'not investment advice' lines partly restate the read-only annotation, which keeps it from a 5.

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?

Three short sentences, front-loaded with the core scope before source, safety and disclaimer. Slight redundancy between 'Read-only, never places orders' and the readOnlyHint/destructiveHint annotations costs it a point, but nothing is padded.

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?

With only two optional, fully documented parameters and no output schema, the description covers the essentials: what qualifies as a cluster, the time window, the source, and the shape of results. It omits ordering/limit behavior on the returned ticker list, a minor gap rather than a blocking one.

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% and both parameters already carry ranges and defaults (days 1-14 default 7, minBuyers 2-10 default 3). The description only restates these as 'last N days' and 'several distinct insiders' without adding format or edge-case meaning, so the baseline 3 applies.

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?

The description states a specific verb and resource: it lists tickers where multiple distinct insiders made open-market purchases (Form 4 code P) within a lookback window, and names the returned fields. The 'several distinct insiders' framing implicitly separates it from a single-insider tool like insider_buys, but it never names or contrasts a sibling explicitly, keeping it at 4.

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?

Usage is implied by the cluster definition and the N-day window, so an agent can infer this is for detecting multi-insider buying signals. There is no explicit when-to-use, when-not-to-use, or pointer to the sibling insider_buys for single-buyer cases, so guidance is only adequate.

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