Skip to main content
Glama
Sign In

algoum-mcp

by io.github.fi4all
OverviewDiscussionsAdmin

Latest insider trades (cross-market feed)

insider_list_recent
Read-onlyIdempotent

Cross-market feed of the most recently filed insider trades of all companies, within the last 1 to 30 days.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days, 1 to 30 (default 1).
roleNoInsider role: officer, director, 10%-owner or other.
sideNoTrade direction: buy, sell or both (default both).
limitNoMaximum number of results, 1 to 500 (default 50).
cursorNoOpaque cursor from meta.next_cursor of the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 the look-back window (1-30 days) and the all-companies scope, but says nothing about result ordering, pagination behavior despite the cursor parameter, or result volume. Adequate but not rich.

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?

A single front-loaded sentence that states the resource, the cross-market scope and the time window with no filler. Every clause carries information an agent needs.

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?

For a five-parameter, no-output-schema feed tool the description covers what the feed is and its time bounds, which is the minimum viable. It leaves pagination, ordering and expected result volume unstated, though the annotations and 100%-covered schema absorb most of that burden.

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% with five well-documented optional parameters, so the schema carries parameter semantics fully. The description only echoes the 1-30 day window and implies the absence of a ticker filter; it adds no format or syntax detail beyond the schema.

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 specific verb and resource (list insider trades) plus scope (cross-market feed, most recently filed, all companies). 'Cross-market feed of all companies' implicitly distinguishes it from per-ticker siblings like insider_list_transactions, but it never names an alternative 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 is implied by 'cross-market feed ... of all companies', suggesting this is the unfiltered discovery endpoint rather than a ticker-scoped lookup. However, there is no explicit when-to-use statement, no mention of the cluster-buys sibling, and no guidance on when a recent feed is preferable to a targeted transaction 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