Skip to main content
Glama

Stratalize Intelligence

Get Form4 Insider Cluster

get_form4_insider_cluster
Read-only

Use when detecting insider trading clusters from Form 4 filing density over a window. Returns form4_filing_count, cluster_score, and activity signal for a ticker. Source: SEC EDGAR Form 4 cluster analysis. $0.50 USDC per call.

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": "get_form4_insider_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes
days_backNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered structurally. The description adds genuinely useful non-schema context: the data provenance (SEC EDGAR Form 4 cluster analysis) and a concrete price point ($0.50 USDC per call), which matters for an agent deciding whether to spend. It does not explain result scale or limits, so the value-add is real but partial.

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 compact sentences with the use-case trigger front-loaded, followed by outputs, provenance, and cost. Nothing is redundant, though the output-field list and the price could be ordered more crisply relative to the trigger.

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

Completeness3/5

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

There is no output schema, and the description does name the returned fields, source, and cost, which covers most of what an agent needs. It is still incomplete on the optional days_back parameter (no default, no bounds) and on how cluster_score should be interpreted, which matters for a quantitative signal tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry both parameters. It only loosely gestures at them: 'over a window' hints at days_back but never states units, default, or the 7-180 bounds, and ticker is only implied by 'for a ticker'. An agent still has to open the schema to call this correctly.

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 names a specific action (detecting insider-trading clusters) from a specific source (Form 4 filing density over a window) and lists what comes back (form4_filing_count, cluster_score, activity signal) for a ticker. It is distinguishable from a generic insider-trading tool, though it never explicitly contrasts itself with the sibling get_sec_insider_trading.

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 trigger condition 'Use when detecting insider trading clusters from Form 4 filing density' gives clear implied usage context. However, there is no when-not guidance, no stated prerequisites, and no routing to the closely related get_sec_insider_trading sibling.

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