Skip to main content
Glama

News from 8-K filings

news
Read-onlyIdempotent

Return the newest 8-K filings across all companies (or one), each with its items, event types (earnings, acquisition_disposition, leadership_change, restatement, bankruptcy, agreement...), a headline and an importance from 1 to 5. Use importance_min 4 for top stories (earnings, M&A, impairments, auditor changes, restatements, bankruptcies). Importance is FinancialMD's rule by 8-K item number; this is a filing-based feed, not wire news, so follow source_url for the text. Use it for what was filed recently across the market or by one company.

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,
      "importance_min": 4
    },
    "name": "news"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoAccepted on or before (YYYY-MM-DD).
fromNoAccepted on or after (YYYY-MM-DD).
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 200).
cursorNoOpaque cursor from a previous page (data.next_cursor).
companyNoOptional: one company. 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.
event_typeNoOnly filings with an item of this type (earnings, leadership_change, agreement, acquisition_disposition, restatement, bankruptcy, impairment, auditor_change...).
importance_minNoOnly filings whose highest item is at least this important (5 critical, 4 major, 3 notable, 2 routine, 1 exhibits only).

Output Schema

NameRequiredDescriptionDefault
dataNo{ items: [{ company, accession, form, filed, accepted_at, importance, headline, event_types, items: [{ item, title, event_type, importance }], source_url }], 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: -"Optional: one company. 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: +"Optional: one company. 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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured context: that importance is FinancialMD's own rule derived from the 8-K item number, and that this is a filing-based feed rather than editorial wire news, so the text must be fetched via source_url. That is the kind of behavioral caveat an agent could not recover from annotations or schema.

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 statement and the item list are front-loaded, and the follow-up sentences each add new information (importance guidance, source-of-truth caveat, use case) rather than restating the name. The first sentence is long and carries a trailing parenthetical enumeration of event types plus the importance mention, which is slightly dense but still readable. No filler sentences are present.

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?

With 8 parameters, full schema descriptions, an output schema, and complete annotations, the description only needs to supply orientation and semantics, and it does so: what the feed is, how importance is computed, and where the actual text lives. Pagination, date bounds, and company identifier syntax are all handled by the schema. The only mild gap is the absence of any pointer to how this differs from the other filing-oriented tools in the catalog.

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 the schema already defines every parameter, including the importance_min scale and the company identifier formats; that sets the baseline at 3. The description does add meaning by mapping importance 4 to specific high-signal item categories (earnings, M&A, impairments, auditor changes, restatements, bankruptcies), which is semantic guidance beyond the numeric scale. It says nothing further about date-range or cursor behavior, but the schema carries those.

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 opens with a specific verb and resource: 'Return the newest 8-K filings across all companies (or one)', and enumerates what each record carries (items, event types, headline, importance). It also draws a conceptual boundary against wire news, which helps an agent pick it over a news-style tool. It stops short of naming concrete siblings such as filings_list or event_feed, so the differentiation is conceptual 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 Guidelines4/5

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

'Use it for what was filed recently across the market or by one company' gives a clear activation context, and 'Use importance_min 4 for top stories' gives concrete invocation guidance tied to the parameters. The warning to 'follow source_url for the text' tells the agent not to expect article bodies here. There is no explicit when-not-to-use or named alternative, which keeps it below a 5.

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