algoum-mcp

Find cluster buys

insider_list_cluster_buys

Read-onlyIdempotent

Finds companies where several distinct insiders bought within the window. The window filters the transaction date, not the filing date, so the signal may precede the last filing.

Input Schema

Name	Required	Description
`as_of`	No	Point in time, YYYY-MM-DD: compute the clusters as known at the end of that day (Eastern Time), counting only filings submitted by then. Use it for backtests. Omit for today.
`limit`	No	Maximum number of results, 1 to 500 (default 50). This endpoint is not paginated.
`roles`	No	Comma-separated roles counted before aggregation, e.g. officer,director. Omit for all roles.
`window`	No	Aggregation window on the transaction date, e.g. 7d.
`min_insiders`	No	Minimum number of distinct buying insiders.
`exclude_uniform_price`	No	true leaves out clusters whose buyers all bought at the same price (uniform_price) - usually a private placement or a reinvestment plan, not independent decisions.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

addedInput schema / properties / exclude_uniform_price

Added value: +{
+  "description": "true leaves out clusters whose buyers all bought at the same price (uniform_price) - usually a private placement or a reinvestment plan, not independent decisions.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 16, 2026

addedInput schema / properties / as_of

Added value: +{
+  "description": "Point in time, YYYY-MM-DD: compute the clusters as known at the end of that day (Eastern Time), counting only filings submitted by then. Use it for backtests. Omit for today.",
+  "type": "string"
+}

Changed2 schema fields changedOct 3, 2026

removedInput schema / properties / cursor

Removed value: -{
-  "description": "Opaque cursor from meta.next_cursor of the previous page.",
-  "type": "string"
-}

changedInput schema / properties / limit / description

Previous value: -"Maximum number of results, 1 to 500 (default 50)."New value: +"Maximum number of results, 1 to 500 (default 50). This endpoint is not paginated."

First observedOct 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: the window filters the transaction date rather than the filing date, and the signal may precede the last filing — a non-obvious timing trait that materially affects interpretation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with zero filler, and the primary scope statement is front-loaded ahead of the timing caveat. Every clause carries information.

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?

For a six-parameter read-only screening tool with no output schema, the description conveys the result shape (companies with clustered insider buys) and the timing nuance. It stops short of describing result ordering or what fields each cluster contains, but nothing critical to correct invocation is missing.

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%, so all six parameters are already documented in the schema, which sets the baseline at 3. The description reinforces the transaction-date semantics of 'window' but adds no syntax, defaults, or constraints beyond what the schema provides.

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 ('Finds') and a well-defined resource ('companies where several distinct insiders bought within the window'), which is precise enough that an agent can separate it from raw-transaction siblings like insider_list_transactions. It does not, however, name or contrast with any sibling tool explicitly.

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 context is implied rather than stated: the description explains the semantics of the window and the backtest angle lives in the schema, but there is no explicit when-to-use-this-vs-alternatives guidance. An agent must infer that this is the aggregated/screening tool rather than the raw listing tool.

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

All algoum-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?