Skip to main content
Glama

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.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), and the description adds genuinely new context: the SEC EDGAR provenance and a per-call price of $0.50 USDC, which matters for an agent deciding whether to invoke. It omits latency, rate limits, and what 'activity signal' values look like.

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 trigger condition, then outputs, then provenance and price. No filler, though the source line partially restates the tool name.

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?

With no output schema, listing the three return fields is necessary and done. However, for a two-parameter tool with zero schema descriptions, the missing parameter semantics leave an agent guessing at input format, which is a real gap.

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 parameter meaning and does not. It never explains the ticker format (e.g. 'AAPL' vs CIK) or what days_back controls, its 7-180 bounds, or its default; 'over a window' is the only hint.

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?

States a specific verb and resource: detecting insider trading clusters from Form 4 filing density, and names the three return fields. It is distinguishable from get_sec_insider_trading by its density/cluster framing, though it never explicitly contrasts the two.

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?

'Use when detecting insider trading clusters' gives a positive trigger condition, but there is no when-not guidance, no prerequisites, and no named alternative for plain insider-trading lookups despite a close sibling existing.

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