Skip to main content
Glama

Arkanum Data: SEC insider trades

Red-flag 8-Ks across the market

market_warnings
Read-only

The latest 8-K filings across the market that report a red flag: bankruptcy, accelerated debt, delisting notices, restatements, auditor changes, cyber incidents, layoffs. From the last four days, newest first. Pass all=true for every 8-K with a specific item. Hobby and Pro.

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": "market_warnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNo
limitNo
tickerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false), so the description's added value is the recency window (four days), the newest-first ordering, and the explicit list of flag types that qualify. That is real behavioral context an agent could not derive from the schema; only rate limits or result-size behavior are absent.

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 scope and time window come first, followed by the parameter hint and plan note, with no filler sentences. The category enumeration is long but each item earns its place by defining what counts as a red flag.

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 read-only listing tool with no output schema and no required parameters, the description covers the essentials of what is returned. However, it leaves the ticker filter and limit parameter unexplained and never says what a result row contains, which matters given that consumers will want to know how flags are labeled.

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 coverage is 0%, so the description should compensate, and it only partly does: it explains the non-obvious 'all' flag, but the phrasing 'every 8-K with a specific item' is ambiguous rather than clarifying. The 'limit' cap of 500 and the 'ticker' filter are never mentioned, leaving two of three parameters undocumented anywhere.

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 concrete verb+resource (the latest 8-K filings) and enumerates the red-flag categories it surfaces (bankruptcy, delisting, restatements, auditor changes, etc.), which makes its content unambiguous. 'Across the market' plus 'from the last four days, newest first' scopes it apart from watchlist-style siblings without naming them 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?

There is one piece of usage guidance — 'Pass all=true for every 8-K with a specific item' — plus a plan-availability note ('Hobby and Pro'), but no statement of when to prefer this over watchlist_warnings, company_risk_flags, or big_stakes. The agent must infer the broad-market vs. company-scoped distinction itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources