Skip to main content
Glama

8-K events

company_events
Read-onlyIdempotent

Return the 8-K filings of a company, newest first, each with the items the filer selected (2.02 results, 5.02 officer changes, 1.01 agreements, 2.01 acquisitions, 4.02 non-reliance...) classified by event_type, with a headline and an importance from 1 to 5 (importance_min 4 keeps the major ones). A filing-based event feed, not wire news; for all companies use news; follow source_url for the text. Use it when asked what material events one company disclosed.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 10,
      "company": "ticker:AAPL"
    },
    "name": "company_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoKnowledge date or timestamp (YYYY-MM-DD or RFC 3339). The answer is what FinancialMD knew at that instant: only facts whose known interval contains as_of. Omit for the current view.
limitNoMaximum number of periods or items to return (default 20, at most 500).
cursorNoOpaque cursor from a previous page (data.next_cursor).
companyYesCompany identifier: a FinancialMD id ("fmd_01H..."), an SEC CIK ("cik:320193"), or a ticker ("ticker:AAPL", optionally with the MIC "ticker:AAPL.XNAS"). A bare ticker like "AAPL" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI ("lei:IOG4E947OATN0KJYSD45") or its fmd_ id.
event_typeNoOnly filings with an item of this type (earnings, leadership_change, agreement, acquisition_disposition, restatement...).
importance_minNoOnly filings whose highest item is at least this important.

Output Schema

NameRequiredDescriptionDefault
dataNo{ items: [{ accession, form, filed, accepted_at, report_date, source_url, importance, headline, event_types, items: [{ item, title, event_type, importance }] }], next_cursor, note }
metaNoRequest metadata: request_id, as_of, company resolution, coverage, pipeline_version, licence, terms, proof_base.
errorNoPresent only on isError results: the API error code and message plus remedy hints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / company / description
      Previous value: -"Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL."New value: +"Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI (\"lei:IOG4E947OATN0KJYSD45\") or its fmd_ id."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds ordering ('newest first'), the importance scale semantics ('importance_min 4 keeps the major ones'), and the key behavioral fact that the filing text is not returned but reached via source_url. It does not discuss pagination behavior or result caps, which the schema partially covers via cursor/limit.

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 return shape and ordering are front-loaded, then filtering, then the sibling contrast and use case — a sensible order. The middle parenthetical listing item codes is dense but load-bearing; the sentence is long and could be split, which is the only reason this is not a 5.

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?

An output schema exists, so return structure needn't be re-explained; the description nonetheless covers ordering, classification, importance filtering and where to get filing text. For a read-only, well-annotated tool with full schema coverage, the remaining omission — no mention of pagination via cursor — is minor.

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; the description earns above that by enumerating concrete event_type values (2.02 results, 5.02 officer changes, 1.01 agreements, 2.01 acquisitions, 4.02 non-reliance) and by explaining importance_min in operational terms ('4 keeps the major ones'). It adds no clarification for company identifiers or as_of, but those are already richly documented in 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 ('Return the 8-K filings of a company') plus the exact shape of what comes back: items the filer selected, classified by event_type, with headline and importance 1-5. It also draws the boundary against a sibling ('A filing-based event feed, not wire news'), so an agent can distinguish it from a news feed without opening either schema.

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?

Gives both an inclusion rule ('Use it when asked what material events one company disclosed') and an explicit exclusion with the alternative named ('for all companies use news'). It also states a practical next step when detail is needed ('follow source_url for the text'), leaving little to inference.

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