Skip to main content
Glama

FinBridge

Korean Company Financials (DART)

get_dart_financials
Read-only

Fetch financial statements of a Korean company from OpenDART (fnlttSinglAcntAll: full single-company statements) and normalize them to standard metrics. Amounts are raw KRW (no scaling); EPS is KRW per share.

Not this tool for: US statements (get_edgar_financials), a KR-vs-US pair on one screen (compare_financials_kr_us), or ranking many companies at once (screen_companies, which reads the stored table and covers KR/US/TW/JP/EU). This tool requests one Korean company's statements through the DART adapter; results may be reused from a process-local cache for up to 24 hours. data_as_of.generated_at is response creation time, not source retrieval time. Peer comparisons use separately dated database snapshots.

Args:

  • corp: Company: Korean name (e.g. '삼성전자'), 6-digit stock code (e.g. '005930'), or 8-digit DART corp_code (e.g. '00126380')

  • year: business year 2015-2026 (default: last year). Annual reports are filed ~March of the following year (FY2025 filed 2026-03).

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

  • fs: 'consolidated' | 'separate' (default 'consolidated'). If consolidated statements do not exist, automatically retries separate and says so in notes.

  • statement: optional BS/IS/CIS/CF/SCE account-group filter

  • account_query: optional case-insensitive account name or account_id substring

  • account_limit: returned account rows, 1-200 (default 40)

  • as_of: optional YYYY-MM-DD. Adds point_in_time: the version of this period/basis that was public on that day.

  • response_format: 'markdown' (default, tables) or 'json' (compact)

Returns structured {normalized, accounts}:

  • normalized: {company:{name,id,ticker}, basis, periods:[{period, fiscal_year, currency:'KRW', metrics:{revenue, gross_profit, operating_income, net_income, eps_diluted, assets, liabilities, equity, cash_and_equivalents, operating_cash_flow}}], notes}. Annual reports include the prior-year comparative as a second period.

  • accounts: selected reported statement rows with statement, account id/detail, reported order, currency, current and previous amounts.

  • statement_groups: counts and reported order ranges by BS/IS/CIS/CF/SCE. These are flat DART groups, not an inferred XBRL hierarchy.

  • sum_checks: known balance-sheet equations with pass/fail/not_tested, operands, currency, tolerance and receipt-number evidence.

  • preserved_revisions: bounded numeric filing versions for the exact database company, requested period and actual statement basis. Includes provider, metric units, publication-day evidence, latest observation, unknown first-seen state, and explicit comparison uncertainty.

  • revision_links: original filing <-> amendment filings for this period/basis, linked only by DART report names ([기재정정]/[첨부정정] prefix, same title, one original, later receipt numbers). restated_items lists each metric whose value changed with original_value, amended_value, both receipt numbers, both publication dates and both DART URLs. Exact 1,000^k ratios are flagged as suspected unit errors, not restatements. Unlinkable cases return a reason instead of a guess.

  • point_in_time (only with as_of): the last preserved version with publication_date <= as_of (no look-ahead; latest-value fallback is never used). status found | uncertain (an amendment public by as_of has no preserved values) | not_yet_filed | original_not_preserved | no_versions | unavailable.

  • earnings_disclosures (only when stored filings exist for this period): figures the company itself disclosed, next to its periodic-report figures. preliminary_vs_reported = the last 영업(잠정)실적 filing published on or before the periodic report vs that report's original values (difference, difference_pct, within_rounding = within half the preliminary table's unit; window_ambiguous/scale_suspect assert nothing), with every preliminary version, its amendment link (only when exactly one earlier original exists) and unreadable filings. outlook_vs_reported = single-number items from 영업실적등에대한전망/장래사업ㆍ경영계획 for this exact period with achievement_pct = reported ÷ disclosed × 100, or a status explaining why nothing is computed (basis_not_stated, definition_may_differ, period_not_reported_directly …). history = counts of those filings and their amendments since recorded_from. Facts only — no forecast, estimate or recommendation.

Examples:

  • {corp: '삼성전자', year: 2024} -> FY2024+FY2023, revenue ~3.0e14 KRW

  • {corp: '005930', year: 2025, report: 'q1'} -> Q1 2025 (3-month income-statement figures)

  • {corp: '010130', year: 2024, as_of: '2025-06-30'} -> FY2024 as known on 2025-06-30 (before the 2026-08-13 amendment)

Use for KR-listed company fundamentals. Don't use for US companies (get_edgar_financials) or for filings text (get_dart_filings). Errors: 'no data' (DART status 013) -> try another year/report or fs='separate'; unknown company -> run search_dart_company first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fsNoStatement scope: consolidated(연결, CFS) or separate(별도, OFS). Default consolidated.consolidated
corpYesCompany: Korean name (e.g. '삼성전자'), 6-digit stock code (e.g. '005930'), or 8-digit DART corp_code (e.g. '00126380')
yearNoBusiness year (bsns_year), 2015-2026. Default: last year (2025).
as_ofNoOptional YYYY-MM-DD. Return point_in_time: the preserved version of this period that was public on that day.
reportNoReport type: annual(사업보고서) | q1(1분기) | half(반기) | q3(3분기). Default annual.annual
statementNoOptional statement-group filter.
account_limitNoMaximum returned account rows (default 40).
account_queryNoOptional account name/account_id substring.
response_formatNo'markdown' for tables, 'json' for compact machine-readable outputmarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountsNo
data_as_ofNo
normalizedYes
plan_limitNo
sum_checksNo
point_in_timeNo
revision_linksNo
peer_comparisonNo
statement_groupsNo
account_selectionNo
preserved_revisionsNo
earnings_disclosuresNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / earnings_disclosures
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {},
      +  "type": "object"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / as_of
      Added value: +{
      +  "description": "Optional YYYY-MM-DD. Return point_in_time: the preserved version of this period that was public on that day.",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +  "type": "string"
      +}
    • addedOutput schema / properties / point_in_time
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / revision_links
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {},
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / preserved_revisions
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {},
      +  "type": "object"
      +}
  4. Changed6 schema fields changed
    • addedInput schema / properties / account_limit
      Added value: +{
      +  "default": 40,
      +  "description": "Maximum returned account rows (default 40).",
      +  "maximum": 200,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / account_query
      Added value: +{
      +  "description": "Optional account name/account_id substring.",
      +  "maxLength": 100,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / statement
      Added value: +{
      +  "description": "Optional statement-group filter.",
      +  "enum": [
      +    "BS",
      +    "IS",
      +    "CIS",
      +    "CF",
      +    "SCE"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / account_selection
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / statement_groups
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "properties": {},
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / sum_checks
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "properties": {},
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  5. Changed3 schema fields changed
    • addedOutput schema / properties / data_as_of
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {},
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / peer_comparison
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {},
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / plan_limit
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {},
      +  "type": "object"
      +}
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish readOnly, openWorld, and non-destructive behavior, but the description adds substantial operational context: 24-hour cache reuse, response creation time vs source retrieval time, automatic consolidated-to-separate fallback, no-look-ahead point-in-time semantics, revision linking rules, and earnings disclosure handling. These are meaningful behavioral traits beyond the structured hints.

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 definition is front-loaded with purpose and exclusions, then organized into Args, Returns, Examples, and Errors. It is very long and repeats some schema parameter details, but most of the detail earns its place given the tool's complexity and the subtle financial semantics involved.

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 a complex nine-parameter financial data tool with an output schema, the description is exceptionally complete. It covers purpose, alternatives, parameter behavior, return semantics, edge cases, revision handling, point-in-time behavior, and error recovery.

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 the baseline is 3. The description does add useful meaning beyond the schema, including filing timing, automatic fs fallback behavior, case-insensitive account querying, and the no-look-ahead semantics of as_of, though much of the Args section still mirrors 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: fetch and normalize financial statements of a Korean company from OpenDART. It also names the function (fnlttSinglAcntAll) and explicitly distinguishes the tool from sibling tools like get_edgar_financials, compare_financials_kr_us, and screen_companies.

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?

Provides explicit when-to-use and when-not-to-use guidance, naming alternatives for US statements, KR-vs-US comparison, bulk screening, and filing text. It also gives error handling guidance and examples for common query patterns.

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.