Skip to main content
Glama

Arkanum Data: SEC insider trades

Insiders buying or selling together

insider_clusters
Read-only

Stocks where two or more officers or directors bought (or sold) within the same window, most insiders first. Hobby and Pro.

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
daysNo
sideNobuy
limitNo
min_insidersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds two useful facts beyond that: results are sorted 'most insiders first', and access is limited to 'Hobby and Pro' tiers, which signals a plan-level access constraint. It says nothing about result volume or how the window interacts with the days parameter.

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?

Two short sentences with the core definition front-loaded and no filler. The trailing 'Hobby and Pro' is compact but cryptic — a reader cannot tell whether it means availability, a data source, or a tier requirement.

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?

It is a read-only list tool with no output schema, so return-value explanation is not required, and the safety profile is carried by annotations. Still, with four undocumented parameters and no description of what a returned row contains (ticker, insider count, window dates), the definition leaves real gaps for an agent composing a call.

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 every parameter (days, side, limit, min_insiders) is documented only by its type, default and bounds. The description hints at min_insiders by saying 'two or more' and implies side via 'bought (or sold)', but never explains what the days window measures or how limit/ordering interact, so it does not compensate for the coverage gap.

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 concrete resource and filter: stocks where two or more officers or directors bought or sold within the same window, ordered by insider count. That is specific enough to distinguish it from a generic insider-trade search, though it never names a sibling to contrast with.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative (search_insiders, unusual_insider_buys, latest_insider_trades all plausibly overlap). The concept of a 'cluster' implies a screening use case, but the agent must infer that itself.

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