Skip to main content
Glama

List a US company's latest 8-K filings and their items

sec_events
Read-only

The latest 8-K current reports of a US company (ticker or CIK) with their item codes explained in plain words (1.01 material agreement, 2.02 results, 5.02 executive change and so on). Each filing links to its document. US government data. Related tools on this server, for a different need: sec_filings when you need to list recent SEC EDGAR filings for a company; sec_insiders when you need to list the latest Form 4 insider trades of a US company. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "sec_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1 to 20 (default 10)
companyYesTicker or CIK

Output Schema

NameRequiredDescriptionDefault
cikNo
sourceNo
companyNo
filingsNo
checkedAtNo
matchedByNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description goes further by disclosing cost ($0.002 per successful call), the payment rail (x402, USDC on Base/Solana and others), and that failed calls are not charged — commercially important context an agent cannot get elsewhere. It stops short of describing result volume, freshness, or rate limits, so it is strong rather than complete.

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?

The capability and its distinguishing feature (plain-language item codes, document links) lead, followed by sibling routing and then pricing — a sensible front-loaded order. The parenthetical item examples (1.01, 2.02, 5.02) are compact and genuinely informative; 'US government data' is the only mildly redundant clause.

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?

The tool is simple (2 params, full schema coverage, output schema present), and the description covers purpose, alternatives, and payment mechanics without needing to explain return values. Minor gaps remain, such as the apparent cap on how many filings are returned and whether non-US issuers are handled, but nothing essential for a correct call is missing.

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 both parameters are already documented in the input schema, including the limit range of 1–20 with a default of 10. The description only restates 'ticker or CIK' for the company field and says nothing about the limit parameter, so it adds essentially no meaning beyond the schema.

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 — the latest 8-K current reports of a US company, identified by ticker or CIK — and adds that item codes are explained in plain words with a link to each document. That level of specificity (item decoding + document links) separates it cleanly from sec_filings and sec_insiders without needing their schemas.

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

Usage Guidelines5/5

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

The description explicitly names two alternatives and the condition under which each should be chosen: sec_filings for general recent EDGAR filing lists, sec_insiders for Form 4 insider trades. It frames them as 'for a different need,' making the routing decision unambiguous.

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