Skip to main content
Glama
datavidence

datavidence-financials

Official
by datavidence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get restatement history

get_revisions
Read-onlyIdempotent

Trace how a company's reported figures changed across filings, showing each restatement with filing date and EDGAR link. Identify restatements and view the full history for any metric.

Instructions

Show how a company's reported figures for a fiscal year CHANGED across filings — as originally reported, then each restatement.

A company re-reports every fiscal year as a comparative in later filings, and when a number changes, that is a restatement. This returns the full series for each metric: every reported value with the date it was filed, the form (10-K/10-Q), the SEC accession and a direct EDGAR link, plus whether it was restated and by how much.

Use it to answer "has this been restated?", to show a figure's history, or to explain why a backtest on today's data would not match what an investor could have known at the time. Identify the company by ticker OR cik; narrow with metrics (comma-separated, e.g. "total_revenue,net_income") or omit for all. get_financials returns the LATEST reported figure; its as_of parameter returns the value as known on a date; this shows the whole series at once.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikNoSEC Central Index Key, e.g. "0000320193". Give this or `ticker`.
yearYesFiscal year, e.g. 2023.
tickerNoStock ticker, e.g. "AAPL". Give this or `cik`.
metricsNoComma-separated metric names, e.g. "total_revenue,net_income". Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / cik / description
      Added value: +"SEC Central Index Key, e.g. \"0000320193\". Give this or `ticker`."
    • addedInput schema / properties / metrics / description
      Added value: +"Comma-separated metric names, e.g. \"total_revenue,net_income\". Omit for all."
    • addedInput schema / properties / ticker / description
      Added value: +"Stock ticker, e.g. \"AAPL\". Give this or `cik`."
    • addedInput schema / properties / year / description
      Added value: +"Fiscal year, e.g. 2023."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes beyond readOnly/idempotent annotations by detailing the exact returned content: every reported value with filing date, form, SEC accession, EDGAR link, restated flag, and magnitude. It also explains the restatement concept, which helps the agent interpret results correctly.

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 description is front-loaded with the core behavior, then returned fields, then use cases and parameters. Every sentence carries unique information, including the sibling contrast.

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?

Even without an output schema, the description enumerates the returned fields and fully covers parameter behavior. It addresses the closest alternative tool and typical use cases, so an agent has everything needed to select and invoke it correctly.

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 documents ticker/cik and metrics. The description reinforces the ticker-OR-cik requirement and provides a metrics example, but adds no substantive semantics 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-resource pair: show how reported figures for a fiscal year changed across filings. It distinguishes itself from the closest sibling, get_financials, by contrasting the whole series with the latest figure.

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?

Explicitly lists when to use it: answering whether a figure was restated, showing a figure's history, and explaining backtest mismatches. It also names the alternative (get_financials and its as_of parameter) and explains why this tool is chosen instead.

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

Deploy Server

Other Tools