Skip to main content
Glama

FinBridge

Korean Financials by Filing Version (DART)

get_dart_revision_history
Read-only

List every filed version of one Korean periodic report — the original and each [기재정정]/[첨부정정] amendment — with its statement totals, so a period can be read as it stood on any date, including intermediate amendments.

Not this tool for: the current statements (get_dart_financials), filing text (get_dart_document), US filers (get_edgar_financials).

Versions come from FinBridge's DART filings index (same company, same report title, amendment prefix). Values come from the stored as-reported history where present; a version without stored values is read on request from that receipt's own XBRL (OpenDART fnlttXbrl.xml) with the same extraction rule and unit-scale guard as the as-reported history, then cached. Source calls per request are capped and metered against the shared DART daily quota; a version not fetched says why in value_status. Values are never inferred.

Args:

  • corp: Korean name, 6-digit stock code or 8-digit DART corp_code

  • year: business year 2015-2026 (default: last year)

  • report: 'annual' | 'q1' | 'half' | 'q3' (default 'annual')

  • period_end: optional YYYY-MM, the period in the report title (e.g. '2025-04' for 반기보고서 (2025.04)). Needed only when status is 'ambiguous'.

  • fs: 'consolidated' | 'separate' (default 'consolidated')

  • as_of: optional YYYY-MM-DD — adds point_in_time: the last version with values public on that day

  • fetch_missing: default true. false = answer from stored and cached values only (no DART call)

  • response_format: 'markdown' (default) or 'json'

Fiscal years: December year-ends use the titles 사업보고서 (FY.12), 분기보고서 (FY.03), 반기보고서 (FY.06), 분기보고서 (FY.09). Other year-ends (March, June, …, and REITs with six-month fiscal periods) use the company's own fiscal calendar built from its annual-report titles: fiscal_year is the calendar year the fiscal period starts (June year-end FY2024 = 2024-07..2025-06, so its Q3 is 분기보고서 (2025.03)). In a six-month fiscal period the annual report covers six months and the half-year report three months. When two reports of the same type fall in one fiscal_year (six-month REITs), status is 'ambiguous' with candidates; call again with period_end. Fiscal periods of other lengths and periods before the first recorded annual report are not covered.

Returns: {company, fiscal_year, quarter, basis, report_title, period_rule december|fiscal_calendar, fiscal_period {start, end, months}, report_period_end, status complete|partial|no_filings|ambiguous, candidates?, versions:[{receipt_id, role original|amendment|unknown, report_name, publication_date, document_url, values_preserved, value_source financials_revisions|ondemand_cache|ondemand_fetch, value_origin, value_status, reason, currency, metrics, income_window, cash_flow_window, metrics_cumulative, cumulative_window, cumulative_status, cumulative_reason, insurance_concepts}], point_in_time?, source_calls, notes, data_as_of}. Periods: income_window is the period of the income-statement items in metrics (revenue, gross_profit, operating_income, net_income, eps_diluted): annual '12m', q1 '3m', half '6m_cumulative', q3 '3m' (the third quarter alone; July-September for December year-ends). Six-month fiscal periods: annual '6m_cumulative', half '3m'. operating_cash_flow is year to date (cash_flow_window). metrics_cumulative holds the income items year to date (cumulative_window; q3 '9m_cumulative', read from that receipt's XBRL — other reports repeat metrics). cumulative_status: same_as_metrics | from_receipt_xbrl | no_cumulative_context | not_fetched | unavailable; when null, cumulative_reason says why. Year-to-date figures are never derived by adding quarters. Insurers (IFRS 17): where the standard tags are absent, revenue is insurance revenue (ifrs-full:InsuranceRevenue, 보험수익) and operating_income is ifrs-full:ProfitLossFromOperatingActivities (영업이익); insurance_concepts says so per version. value_status: preserved | cached | fetched | no_xbrl | no_facts | no_statement_for_basis | scale_suspect | mixed_currency | fetch_failed | dart_error | not_fetched_request_cap | not_fetched_daily_cap | not_fetched_shared_ceiling | not_fetched_busy | not_fetched_disabled | not_fetched_no_key. point_in_time.status (shared contract with get_dart_financials as_of): found (values public by as_of) | uncertain (values returned, but a later filing public by as_of has no values) | not_yet_filed (no filing public by as_of) | no_values (filings public by as_of, none with values) | no_versions (no filing or version known at all) | ambiguous (report not determined; pass period_end). point_in_time.scale_suspect: the picked version is 1,000^k off another valued version (a flag, not a status; value_status scale_suspect means the guard rejected that version).

Examples:

  • {corp: '010130', year: 2024, as_of: '2025-04-15'} -> Korea Zinc FY2024 as known after the 2025-03-31 amendment

  • {corp: '삼성전자', year: 2024, fetch_missing: false} -> versions from stored values only

  • {corp: '010130', year: 2023, report: 'q3'} -> Korea Zinc Q3 2023: July-September in metrics, January-September in metrics_cumulative

  • {corp: '001080', year: 2024, report: 'q3', fs: 'separate'} -> June year-end: 분기보고서 (2025.03), metrics_cumulative 2024-07..2025-03

  • {corp: '432320', year: 2025, report: 'half', period_end: '2025-04'} -> six-month REIT: 반기보고서 (2025.04), three months

Errors: unknown company -> run search_dart_company; years outside the account's history range are refused like get_dart_financials.

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": {
      "corp": "<corp>"
    },
    "name": "get_dart_revision_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
fsNoconsolidated (연결) or separate (별도)consolidated
corpYesKorean name, 6-digit stock code, or 8-digit DART corp_code
yearNoBusiness year 2015-2026 (default 2025). Non-December year-ends: the calendar year the fiscal period starts (may differ from DART's own business-year label).
as_ofNoOptional YYYY-MM-DD: add point_in_time for that day.
reportNoannual | q1 | half | q3 (default annual)annual
period_endNoOptional YYYY-MM of the report title period; picks one report when status is 'ambiguous'.
fetch_missingNoFetch unpreserved versions' XBRL from DART (capped). false = stored/cached only.
response_formatNo'markdown' or 'json'markdown

Output Schema

NameRequiredDescriptionDefault
basisYes
notesNo
reasonNo
statusYes
companyYes
quarterYes
versionsYes
link_ruleNo
candidatesNo
data_as_ofNo
fiscal_yearYes
period_ruleNo
report_titleYes
source_callsNo
fiscal_periodNo
point_in_timeNo
report_period_endNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / candidates / items / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / company / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / data_as_of / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / fiscal_period / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / point_in_time / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / source_calls / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / versions / items / additionalProperties
      Previous value: -trueNew value: +{}
  2. Changed7 schema fields changed
    • addedInput schema / properties / period_end
      Added value: +{
      +  "description": "Optional YYYY-MM of the report title period; picks one report when status is 'ambiguous'.",
      +  "pattern": "^\\d{4}-(0[1-9]|1[0-2])$",
      +  "type": "string"
      +}
    • changedInput schema / properties / year / description
      Previous value: -"Business year 2015-2026 (default 2025)."New value: +"Business year 2015-2026 (default 2025). Non-December year-ends: the calendar year the fiscal period starts (may differ from DART's own business-year label)."
    • addedOutput schema / properties / candidates
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "properties": {},
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / fiscal_period
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {},
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / period_rule
      Added value: +{
      +  "enum": [
      +    "december",
      +    "fiscal_calendar"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / report_period_end
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / status / enum
      Previous value: -[
      -  "complete",
      -  "partial",
      -  "no_filings"
      -]New value: +[
      +  "complete",
      +  "partial",
      +  "no_filings",
      +  "ambiguous"
      +]
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark this read-only and open-world, and the description adds real behavior beyond them: source calls are capped and metered against a shared DART daily quota, uncached versions may be fetched from the receipt's own XBRL then cached, values are never inferred, and a skipped fetch reports why via value_status. The enumeration of value_status and point_in_time.status codes makes failure modes legible before the call.

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?

Front-loaded and organized with labeled sections (Not this tool for / Args / Returns / Examples / Errors), and no sentence is filler. It is still very long and the Returns block re-enumerates a return contract that already exists as an output schema, so some text could be trimmed; density is the cost of an unusually complex tool.

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?

For an 8-parameter tool with fiscal-calendar edge cases, insurers, currency/scale guards, and a shared quota, the description covers period windows (income_window, cash_flow_window, metrics_cumulative), the no-derivation rule, and the full status vocabulary. An agent could call it correctly first try, including the ambiguous retry path.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds meaning the schema cannot: fiscal_year is the calendar year the fiscal period starts (June year-end FY2024 = 2024-07..2025-06), period_end is needed only when status is 'ambiguous', fetch_missing=false suppresses DART calls, and as_of adds a point_in_time view. It also clarifies the corp input accepts name, 6-digit code, or 8-digit corp_code.

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 ('List every filed version of one Korean periodic report'), including the [기재정정]/[첨부정정] amendment scope and the statement totals returned. It then explicitly excludes the siblings it could be confused with ('Not this tool for: the current statements (get_dart_financials), filing text (get_dart_document), US filers (get_edgar_financials)'), so the agent can route without opening a 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?

Names alternatives and the conditions that select them, adds an error path ('unknown company -> run search_dart_company'), and explains the ambiguous-status branch with the exact remedy (call again with period_end). Five worked examples cover the ambiguous, stored-only, non-December, and six-month REIT cases, which is unusually explicit when-to-use guidance.

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.