Skip to main content
Glama

insider_buy_clusters

Identify stocks where three or more insiders made open-market purchases within 24-48 hours, signaling potential bullish activity. Excludes awards and gifts.

Instructions

Form 4 insider buy clusters (3+ insiders bought same ticker in 24-48h). Bullish signal. Filtered to open-market purchases (P code), excluding awards/gifts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
window_hoursNo
min_insidersNo
Behavior3/5

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

With no annotations, the description bears full burden. It discloses key filters (P code, excluding awards/gifts) and time window, but does not explain if it returns historical data, requires authentication, or has rate limits. Adequate but not comprehensive.

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?

The description is concise at two sentences, front-loading the core purpose and key filter. It avoids waste but could structure the information more clearly.

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?

Given the lack of annotations, output schema, and simple parameters, the description provides the essential idea and filter. However, it omits output format and any request/response details, leaving some gaps for agent usage.

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 0%, so the description must add meaning. It hints at parameters with '24-48h' and '3+ insiders', matching defaults, but does not explicitly describe the parameters' purpose, ranges, or constraints, leaving the schema largely unexplained.

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?

The description clearly states the tool identifies insider buy clusters (3+ insiders in 24-48h) from Form 4 filings, with filtering to open-market purchases. This verb-resource pair distinguishes it from sibling tools covering airdrops, ETFs, vaults, macro, etc.

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?

The description provides no explicit guidance on when to use this tool versus its siblings. While 'Bullish signal' implies a use case, there is no mention of alternatives, prerequisites, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FalsifyLab/falsifylab-alpha-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server