Skip to main content
Glama
Sign In

algoum-mcp

by io.github.fi4all
OverviewDiscussionsAdmin

Search material events

events_list
Read-onlyIdempotent

Searches material events (SEC Form 8-K) such as leadership changes, mergers, bankruptcies or cyber incidents 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": "events_list"
  }
}

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.
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.
event_typeNoEvent type: bankruptcy, cyber_incident, leadership_change, delisting, earnings_release, merger_acquisition, capital_action, accounting_issue, auditor_change, late_filing or other_material_event.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, openWorld), so the bar is lower. The description still adds two behavioral facts beyond the schema: results are sorted 'newest filing first', and ticker-or-cik is a hard requirement despite the schema listing no required fields. No pagination or return-shape detail, but the ordering and constraint disclosure are substantive.

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 tightly written sentences: the first identifies the resource, examples, scope and sort order; the second states the input constraint. Nothing is padded and the identity of the tool is front-loaded.

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?

With no output schema, the description should carry return-value burden, and it partially does by disclosing sort order and pagination-nullable cursor plus the ticker/cik requirement. It stops short of describing what a result record contains, but for a read-only list tool with full schema coverage this is close to complete.

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 (to, from, cik, limit, cursor, ticker, event_type) is already fully documented in the schema. The description adds only framing context ('SEC Form 8-K') and no syntax or semantic detail beyond the schema, 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?

States a specific verb and resource ('Searches material events (SEC Form 8-K)') with concrete examples of event categories and a scope qualifier ('of one company'). It differentiates from events_get by being a search/list, but does not explicitly distinguish itself from events_list_recent, which shares nearly identical framing.

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?

The description gives one precondition — 'Either ticker or cik is required' — which is genuine usage guidance since the schema marks zero required parameters. However, it never says when to pick this tool over the sibling events_list_recent or events_get, so the agent must infer the choice.

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