Skip to main content
Glama

Recent 8-K material events from SEC EDGAR

sec_events
Read-only

Recent Form 8-K current reports (material corporate events) for a ticker or CIK over the last 1 to 365 days: filing date, event date, accession number, document URL and item numbers decoded to their Form 8-K titles (1.01 material agreement, 2.02 earnings results, 5.02 director or officer changes, 7.01 Reg FD, 8.01 other events and more), plus counts by item. Source: SEC EDGAR submissions API. Price: $0.005 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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

Input Schema

NameRequiredDescriptionDefault
cikNoSEC Central Index Key, 1 to 10 digits. Mutually exclusive with ticker.
daysNoLook-back window in days, 1 to 365 (default 90): 8-Ks filed on or after today minus days (Eastern Time).
limitNo8-K filings to list, 1 to 50 (default 20), newest first. Item counts cover the whole window.
tickerNoStock ticker, e.g. AAPL or BRK.B. Mutually exclusive with cik.
amendmentsNoAlso include 8-K/A amendments (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered, and the description goes well beyond them: it names the source (SEC EDGAR submissions API), discloses billing terms ($0.005 per successful call in USDC via x402 v2, no charge for failed or empty results), and enumerates the returned fields. The pricing and empty-result behavior are exactly the kind of operational context an agent cannot get from the schema. It does not discuss rate limits, pagination, or error/latency behavior, which keeps it below a 5.

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 definition is front-loaded with the resource and scope, then fields, then source and price, so the agent reads the important parts first. The long parenthesized item-code glossary is information-dense rather than filler and is worth its space, but the single run-on sentence structure makes it heavier than it needs to be; a break between capability and billing would improve scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five optional parameters, full schema coverage, and no output schema, the agent needs to know scope, return shape, data source, and cost – and the description supplies all four, including the exact item-title mapping and the fact that empty matches are free. Nothing material for correct invocation appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds a genuinely non-obvious semantic: "Item counts cover the whole window" – meaning the limit parameter truncates only the listed filings, not the item-count aggregates. It also reinforces that the query works by ticker or CIK and that the window is measured in days with Eastern Time boundaries, both of which matter for interpreting results.

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 tool is presented as "Recent Form 8-K current reports (material corporate events) for a ticker or CIK over the last 1 to 365 days" and then lists exactly which fields are returned (filing date, event date, accession number, document URL, item titles, item counts). The named item-code glossary (1.01, 2.02, 5.02, 7.01, 8.01) pins down the scope as specifically 8-K, which implicitly separates it from the broad sec_filings/sec_search siblings. However, it never names an alternative tool or explicitly states when to use a sibling instead, so the differentiation is implied rather than explicit.

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 only implied: an agent can infer this is the tool for recent material-event 8-Ks on a single company, and the 1-365 day window signals it is not for historical archives. There is no explicit when-to-use/when-not-to-use guidance and no mention of the sec_filings or sec_search alternatives, leaving the routing decision to inference from the resource name alone.

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