Skip to main content
Glama

Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Restatement Radar Feed

list_restatements
Read-onlyIdempotent

List financial-statement restatements — facts a later SEC filing materially changed (>0.5% swing) from what was originally reported. Each event carries the as-reported value, the restated value, the signed delta, a severity bucket, the RAW XBRL tag both filings used (the diff is same-tag, so it is apples-to-apples and checkable), both filings' accession numbers for one-click lineage, an analyst-importance tier (1 headline / 2 statement line / 3 footnote), the fact's rank within the company's restatement history, and — crucially — HOW the company told the market (disclosure_class): non_reliance (it filed an 8-K Item 4.02 telling the SEC not to rely on its prior financials), amended (a 10-K/A or 10-Q/A), or undisclosed (the number changed inside a routine 10-Q/10-K — no amendment, no 4.02). About 94% of events are undisclosed: most numbers that change, change quietly. undisclosed is a statement about the FILING CHAIN, not about the filer's intent — adopting a new accounting standard (ASC 606, ASC 842) legitimately restates prior comparatives with nobody doing anything wrong. Do NOT describe these as fraud, concealment, or wrongdoing. Filter by ticker, sector, severity, minimum swing, importance, disclosure class, or filing date; sort by recency (default) or significance; paginate with the returned cursor. Public data — available on every tier. Provenance: derived from SEC EDGAR filings; verify any figure with verify_fact_lineage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNo'recent' = newest restating filing first (a market-wide radar). 'significance' = importance tier, then swing size (one company's history).recent
limitNoPage size (1-100, default 25).
cursorNoOpaque pagination cursor from a prior response's next_cursor.
sectorNoRestrict to one GICS-style sector (e.g. 'Technology').
tickerNoRestrict to one company — ticker (e.g. 'AAPL') or CIK (e.g. '0000320193').
event_idNoFetch exactly one event by its id (from a prior response).
severityNohigh = |Δ|≥10%, medium = ≥2%, low = ≥0.5%.
disclosureNoFilter by HOW the company told the market. 'non_reliance' = it filed an 8-K Item 4.02 ('Non-Reliance on Previously Issued Financial Statements') — formally telling the SEC not to rely on what it already reported. The loudest signal in US disclosure, and rare. 'amended' = corrected in a 10-K/A or 10-Q/A. 'undisclosed' = the value changed inside a ROUTINE 10-Q or 10-K: no amendment, no 4.02, the old number is simply gone. ~94% of events. Anyone can parse an 8-K, so anyone can list what companies ANNOUNCED; finding what they didn't requires every vintage back to 1993.
filed_sinceNoOnly restatements FILED on or after this date — the 'what changed recently' window.
max_importanceNoOnly lines at or above this importance tier: 1 = headline only (revenue, net income, EPS, total assets, operating cash flow), 2 = + primary statement lines, 3 = everything incl. footnotes. Severity says how far a number moved; importance says whether anyone cares.
amendments_onlyNoOnly restatements that arrived in an AMENDED filing (10-K/A, 10-Q/A) — the company formally telling the SEC it got a number wrong. The sharpest cut there is: it separates real restatements from routine re-files (a next-year 10-K carrying a revised comparative).
min_abs_delta_pctNoOnly events whose absolute restatement is at least this percent (e.g. 5 = ≥5% swings).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
_metaYesProvenance envelope — data lineage for every MCP response
totalYes
eventsYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / _meta / properties / fundamentals_as_of / description
      Previous value: -"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to."New value: +"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt in bulk. Use THIS — not `last_updated` — when telling a user how current the cross-sectional fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to. It is a floor for a single filer, not a ceiling: a filer with a live partition receives its filing, facts and ratios intraday (minutes after EDGAR dissemination), so an entity-scoped read may carry a filing newer than this; cross-sectional ranks (factor scores, earnings signals) refresh with the weekly bulk export."
  2. Changed2 schema fields changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Restrict to one company (e.g. 'AAPL')."New value: +"Restrict to one company — ticker (e.g. 'AAPL') or CIK (e.g. '0000320193')."
    • changedInput schema / properties / ticker / pattern
      Previous value: -"^[A-Za-z.\\-]+$"New value: +"^[A-Za-z0-9.\\-]+$"
  3. Changed2 schema fields changed
    • addedOutput schema / properties / _meta / properties / fundamentals_as_of
      Added value: +{
      +  "description": "ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / _meta / properties / price_as_of
      Added value: +{
      +  "description": "ISO timestamp when the price surfaces were last refreshed.",
      +  "type": "string"
      +}
  4. Changed3 schema fields changed
    • addedOutput schema / properties / events / items / properties / current_primary_doc
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / events / items / properties / first_primary_doc
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / events / items / required
      Previous value: -[
      -  "event_id",
      -  "cik",
      -  "ticker",
      -  "company_name",
      -  "sector",
      -  "concept",
      -  "standard_concept",
      -  "concept_label",
      -  "concept_importance",
      -  "statement_type",
      -  "period_start",
      -  "period_end",
      -  "fiscal_period",
      -  "unit",
      -  "first_value",
      -  "current_value",
      -  "delta_abs",
      -  "delta_pct",
      -  "version_count",
      -  "first_filed_at",
      -  "last_filed_at",
      -  "first_accession",
      -  "current_accession",
      -  "restated_in_form",
      -  "restated_in_amendment",
      -  "disclosure_class",
      -  "severity",
      -  "company_rank"
      -]New value: +[
      +  "event_id",
      +  "cik",
      +  "ticker",
      +  "company_name",
      +  "sector",
      +  "concept",
      +  "standard_concept",
      +  "concept_label",
      +  "concept_importance",
      +  "statement_type",
      +  "period_start",
      +  "period_end",
      +  "fiscal_period",
      +  "unit",
      +  "first_value",
      +  "current_value",
      +  "delta_abs",
      +  "delta_pct",
      +  "version_count",
      +  "first_filed_at",
      +  "last_filed_at",
      +  "first_accession",
      +  "current_accession",
      +  "restated_in_form",
      +  "first_primary_doc",
      +  "current_primary_doc",
      +  "restated_in_amendment",
      +  "disclosure_class",
      +  "severity",
      +  "company_rank"
      +]
  5. Changed2 schema fields changed
    • addedOutput schema / properties / events / items / properties / period_start
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / events / items / required
      Previous value: -[
      -  "event_id",
      -  "cik",
      -  "ticker",
      -  "company_name",
      -  "sector",
      -  "concept",
      -  "standard_concept",
      -  "concept_label",
      -  "concept_importance",
      -  "statement_type",
      -  "period_end",
      -  "fiscal_period",
      -  "unit",
      -  "first_value",
      -  "current_value",
      -  "delta_abs",
      -  "delta_pct",
      -  "version_count",
      -  "first_filed_at",
      -  "last_filed_at",
      -  "first_accession",
      -  "current_accession",
      -  "restated_in_form",
      -  "restated_in_amendment",
      -  "disclosure_class",
      -  "severity",
      -  "company_rank"
      -]New value: +[
      +  "event_id",
      +  "cik",
      +  "ticker",
      +  "company_name",
      +  "sector",
      +  "concept",
      +  "standard_concept",
      +  "concept_label",
      +  "concept_importance",
      +  "statement_type",
      +  "period_start",
      +  "period_end",
      +  "fiscal_period",
      +  "unit",
      +  "first_value",
      +  "current_value",
      +  "delta_abs",
      +  "delta_pct",
      +  "version_count",
      +  "first_filed_at",
      +  "last_filed_at",
      +  "first_accession",
      +  "current_accession",
      +  "restated_in_form",
      +  "restated_in_amendment",
      +  "disclosure_class",
      +  "severity",
      +  "company_rank"
      +]
  6. Changed3 schema fields changed
    • addedInput schema / properties / disclosure
      Added value: +{
      +  "description": "Filter by HOW the company told the market. 'non_reliance' = it filed an 8-K Item 4.02 ('Non-Reliance on Previously Issued Financial Statements') — formally telling the SEC not to rely on what it already reported. The loudest signal in US disclosure, and rare. 'amended' = corrected in a 10-K/A or 10-Q/A. 'undisclosed' = the value changed inside a ROUTINE 10-Q or 10-K: no amendment, no 4.02, the old number is simply gone. ~94% of events. Anyone can parse an 8-K, so anyone can list what companies ANNOUNCED; finding what they didn't requires every vintage back to 1993.",
      +  "items": {
      +    "enum": [
      +      "non_reliance",
      +      "amended",
      +      "undisclosed"
      +    ],
      +    "type": "string"
      +  },
      +  "maxItems": 3,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • addedOutput schema / properties / events / items / properties / disclosure_class
      Added value: +{
      +  "enum": [
      +    "non_reliance",
      +    "amended",
      +    "undisclosed"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / events / items / required
      Previous value: -[
      -  "event_id",
      -  "cik",
      -  "ticker",
      -  "company_name",
      -  "sector",
      -  "concept",
      -  "standard_concept",
      -  "concept_label",
      -  "concept_importance",
      -  "statement_type",
      -  "period_end",
      -  "fiscal_period",
      -  "unit",
      -  "first_value",
      -  "current_value",
      -  "delta_abs",
      -  "delta_pct",
      -  "version_count",
      -  "first_filed_at",
      -  "last_filed_at",
      -  "first_accession",
      -  "current_accession",
      -  "restated_in_form",
      -  "restated_in_amendment",
      -  "severity",
      -  "company_rank"
      -]New value: +[
      +  "event_id",
      +  "cik",
      +  "ticker",
      +  "company_name",
      +  "sector",
      +  "concept",
      +  "standard_concept",
      +  "concept_label",
      +  "concept_importance",
      +  "statement_type",
      +  "period_end",
      +  "fiscal_period",
      +  "unit",
      +  "first_value",
      +  "current_value",
      +  "delta_abs",
      +  "delta_pct",
      +  "version_count",
      +  "first_filed_at",
      +  "last_filed_at",
      +  "first_accession",
      +  "current_accession",
      +  "restated_in_form",
      +  "restated_in_amendment",
      +  "disclosure_class",
      +  "severity",
      +  "company_rank"
      +]
  7. Changed9 schema fields changed
    • addedInput schema / properties / amendments_only
      Added value: +{
      +  "description": "Only restatements that arrived in an AMENDED filing (10-K/A, 10-Q/A) — the company formally telling the SEC it got a number wrong. The sharpest cut there is: it separates real restatements from routine re-files (a next-year 10-K carrying a revised comparative).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / filed_since
      Added value: +{
      +  "description": "Only restatements FILED on or after this date — the 'what changed recently' window.",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / max_importance
      Added value: +{
      +  "description": "Only lines at or above this importance tier: 1 = headline only (revenue, net income, EPS, total assets, operating cash flow), 2 = + primary statement lines, 3 = everything incl. footnotes. Severity says how far a number moved; importance says whether anyone cares.",
      +  "maximum": 3,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "default": "recent",
      +  "description": "'recent' = newest restating filing first (a market-wide radar). 'significance' = importance tier, then swing size (one company's history).",
      +  "enum": [
      +    "recent",
      +    "significance"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / events / items / properties / concept
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / events / items / properties / concept_importance
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / events / items / properties / restated_in_amendment
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / events / items / properties / restated_in_form
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / events / items / required
      Previous value: -[
      -  "event_id",
      -  "cik",
      -  "ticker",
      -  "company_name",
      -  "sector",
      -  "standard_concept",
      -  "concept_label",
      -  "statement_type",
      -  "period_end",
      -  "fiscal_period",
      -  "unit",
      -  "first_value",
      -  "current_value",
      -  "delta_abs",
      -  "delta_pct",
      -  "version_count",
      -  "first_filed_at",
      -  "last_filed_at",
      -  "first_accession",
      -  "current_accession",
      -  "severity",
      -  "company_rank"
      -]New value: +[
      +  "event_id",
      +  "cik",
      +  "ticker",
      +  "company_name",
      +  "sector",
      +  "concept",
      +  "standard_concept",
      +  "concept_label",
      +  "concept_importance",
      +  "statement_type",
      +  "period_end",
      +  "fiscal_period",
      +  "unit",
      +  "first_value",
      +  "current_value",
      +  "delta_abs",
      +  "delta_pct",
      +  "version_count",
      +  "first_filed_at",
      +  "last_filed_at",
      +  "first_accession",
      +  "current_accession",
      +  "restated_in_form",
      +  "restated_in_amendment",
      +  "severity",
      +  "company_rank"
      +]
  8. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the bar is lower. The description goes well beyond annotations by explaining data provenance (SEC EDGAR), the statistical distribution (94% undisclosed), and the nuanced interpretation of disclosure_class (a statement about the filing chain, not intent). It also discloses the reliability markers (same-tag diff, accession numbers) without contradicting any annotation.

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?

Though long, the description is exceptionally dense and well-structured. It front-loads the core purpose, then progresses through event features, interpretive guidance, filters, availability, and provenance. Every sentence earns its place, and there is no fluff or redundancy. For a tool with 12 parameters and complex data semantics, the length is appropriate.

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?

The description covers the operational scope, filtering/sorting/pagination, availability, provenance, interpretation warnings, and a pointer to verification. With an output schema present, return value documentation is unnecessary. The only minor omission is the event_id parameter, but that is a trivial direct lookup and does not affect completeness for an agent.

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 description coverage is 100%, so baseline is 3. The description adds interpretive value beyond the schema: it contrasts severity vs. importance, explains the disclosure_class enum values in depth, and frames filters as use cases. It does not restate parameter details verbatim, but it enriches the semantics, warranting a 4.

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?

The description opens with the specific verb 'List' and a precisely defined resource ('financial-statement restatements'), immediately clarifying what the tool does. It further defines restatements with a concrete threshold (>0.5% swing) and same-tag comparison, making the scope unambiguous. It also distinguishes itself from generic list tools by enumerating unique fields like disclosure_class and accession lineage.

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?

The description provides clear usage context: it is a market-wide radar with filters, sorting by recency or significance, pagination, and availability on every tier. It explicitly recommends verify_fact_lineage for figure verification, indicating a different use case. However, it does not explicitly state 'when not to use this tool' or contrast with sibling list tools, so it stops short of a full when/when-not guide.

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.