Agent Utility Suite (x402)

SEC 8-K material events

sec_recent_events

Read-onlyIdempotent

Answers "What happened at this company lately?": did the CEO or CFO leave, what were the latest earnings, was there an acquisition, major contract or cyber incident. Returns a US public company's most recent 8-K filings from SEC EDGAR, newest first: the material events companies must report within four business days, such as earnings releases (Item 2.02), CEO, CFO and director changes (5.02), material agreements and acquisitions (1.01, 2.01), cybersecurity incidents (1.05), impairments, auditor changes and shareholder votes. Each event has its item codes with official titles, the 8-K text as clean prose, and the text of its press-release exhibits (EX-99), e.g. the full earnings release. Filter by item codes and filing date, or ask for one exact 8-K by accession_number (the free sec_list_filings tool lists them); up to 10 events per call. Look up by stock ticker or CIK. Use it for event monitoring, news and earnings agents, due diligence or trading research, with sec.gov links for citation. If no 8-K matches, you get 404 FILING_NOT_FOUND, free. You are only charged when a result is returned: invalid input (400) and upstream failures (4xx/5xx) are not settled. Costs $0.01 USDC per call via x402. Paid per call with x402 inside MCP (see the server instructions).

Input Schema

Name	Required	Description
`cik`	No	SEC Central Index Key, e.g. 320193. Use this, `ticker` or `company`.
`via`	No	Optional: the tool whose next_calls suggested this call (filled in for you).
`items`	No	Only events reporting one of these 8-K items, e.g. ["5.02"] for executive and director changes, ["2.02"] for earnings releases, ["1.01", "2.01"] for deals, ["1.05"] for cybersecurity incidents.
`limit`	No	How many events to return, newest first (1-10, default 5).
`since`	No	Only events filed on or after this date (YYYY-MM-DD).
`ticker`	No	US stock ticker, e.g. AAPL, MSFT, BRK-B. Use this, `cik` or `company`.
`company`	No	Company name, e.g. "Apple" or "Coca-Cola". Use this, `ticker` or `cik`; a name matching several companies returns their tickers, free.
`accession_number`	No	Return only this 8-K, e.g. one found with the free sec_list_filings tool.
`include_exhibits`	No	Include the text of press-release exhibits (EX-99), e.g. the earnings release. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / via

Added value: +{
+  "description": "Optional: the tool whose next_calls suggested this call (filled in for you).",
+  "maxLength": 64,
+  "type": "string"
+}

Changed3 schema fields changedOct 6, 2026

changedInput schema / properties / cik / description

Previous value: -"SEC Central Index Key, e.g. 320193. Use this or `ticker`."New value: +"SEC Central Index Key, e.g. 320193. Use this, `ticker` or `company`."

addedInput schema / properties / company

Added value: +{
+  "description": "Company name, e.g. \"Apple\" or \"Coca-Cola\". Use this, `ticker` or `cik`; a name matching several companies returns their tickers, free.",
+  "maxLength": 120,
+  "minLength": 2,
+  "type": "string"
+}

changedInput schema / properties / ticker / description

Previous value: -"US stock ticker, e.g. AAPL, MSFT, BRK-B. Use this or `cik`."New value: +"US stock ticker, e.g. AAPL, MSFT, BRK-B. Use this, `cik` or `company`."

First observedOct 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the read-only, idempotent, non-destructive, open-world profile, and the description adds substantial extra context: the four-business-day reporting window, item-code meanings, the 10-event cap per call, and detailed x402 billing behavior (charged only when a result returns, 404 and 400/5xx not settled). This is exactly the kind of behavior an agent cannot infer from structured fields.

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?

Front-loaded with a plain-language framing question and then a structured inventory of return contents, so an agent can skim effectively. It is on the long side, with mild redundancy between the opening example questions and the later item-code list, plus a slightly repetitive x402 pricing sentence.

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 9 parameters, no output schema and no required fields, the description carries the burden well: it explains lookup keys (ticker/CIK/company), filtering, the accession-number mode, what is returned, and the billing/error model. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/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 goes further by decoding item codes (5.02 = executive/director changes, 2.02 = earnings, 1.01/2.01 = deals, 1.05 = cyber) and explaining the accession_number lookup path and per-call limit. It adds real interpretation beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: returns a US public company's most recent 8-K filings from SEC EDGAR, newest first, with item codes, prose text and EX-99 exhibits. It also distinguishes itself from siblings by naming sec_list_filings as the free accession-number lister and contrasting with a generic filing lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete use cases (event monitoring, news/earnings agents, due diligence, trading research) and names an alternative tool, sec_list_filings, for obtaining accession numbers. However, it never states when NOT to use it (e.g. versus sec_earnings_today or sec_alerts_peek), so routing guidance is strong but not exhaustive.

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

All Agent Utility Suite (x402) tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?