Skip to main content
Glama
Sign In

algoum-mcp

by io.github.fi4all
OverviewDiscussionsAdmin

Search insider trades

insider_list_transactions
Read-onlyIdempotent

Searches individual insider trades (SEC Form 4 and 5) of one company, newest filing first. Either ticker or cik is required.

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_list_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day of the window, YYYY-MM-DD, inclusive.
cikNoCentral Index Key; leading zeros optional. Alternative to ticker.
fromNoFirst day of the window, YYYY-MM-DD, inclusive.
roleNoInsider role: officer, director, 10%-owner or other.
sideNoTrade direction: buy or sell.
limitNoMaximum number of results, 1 to 500 (default 50).
cursorNoOpaque cursor from meta.next_cursor of the previous page.
tickerNoStock ticker, e.g. AAPL. Either ticker or cik is required.
form_typeNoFiling source: 4, 5 or an amendment 4/A or 5/A. Amendments are separate rows next to the original and usually repeat it; without the filter both are returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds ordering ('newest filing first') and source filings (Form 4/5), but says nothing about pagination behavior, result volume beyond the schema's limit, or rate limits.

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 no filler; the core purpose is front-loaded and the required-input constraint follows immediately. Nothing could be removed without losing 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 filtered list tool with full schema coverage and explicit annotations, the description covers what it returns (insider trades, newest first) and the minimum input requirement. It is largely complete, though the absence of an output schema leaves the result shape only loosely implied.

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 every parameter including role, side, form_type and cursor is already documented in the schema. The description's 'either ticker or cik is required' partially restates the schema and adds no syntax or format detail, so the baseline 3 applies.

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?

Specific verb and resource ('Searches individual insider trades'), plus scope ('SEC Form 4 and 5', 'one company') and ordering ('newest filing first'). It implicitly distinguishes itself from siblings like insider_list_recent and insider_get_transaction by being per-company, but it never names those alternatives.

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?

It states a hard prerequisite ('Either ticker or cik is required'), which is useful. However it gives no when-to-use guidance versus insider_list_cluster_buys, insider_list_recent, or insider_get_transaction, leaving the agent to infer which sibling suits a given query.

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

All algoum-mcp toolsInspect
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