FinBridge

Explore Korean Disclosure Document (DART)

get_dart_document

Read-only

Explore one DART filing by receipt number while preserving section and table structure — the main body by default, or one of its attachments (audit reports carry the consolidated statements; the main body carries the business description).

Use get_dart_filings first to obtain rcept_no. Start with action='overview', then select a section or table instead of requesting a long flattened filing. The overview lists the archive's entries (main body + attachments with their first heading); pass entry='' to explore an attachment.

Args:

rcept_no: 14-digit DART receipt number
entry: archive entry name from the overview's entries list (default: the main body)
action: overview (default) | section | table | compare_tables | compare_sections
compare_rcept_no and compare_index: second filing and its selected table/section index for comparison; table_index/section_index selects the first. Use both overviews first. Only selected content is compared, not entire filings.
section_index or section_query: one section selector for action='section'
table_index: 1-based table selector for action='table'
max_chars: section text cap, 1,000-100,000 (default 30,000)
max_rows/max_columns: selected table caps (defaults 50/30)
overview_offset/overview_limit: paginate both section and table summaries with the same 0-based slice (defaults 0/20, max 100)
response_format: markdown or json

Returns source evidence for the OpenDART document entry and character range. Tables retain row/column order, cell text, rowspan/colspan and nearby reported unit labels. Zero and negative strings are not discarded. Separate HWP/PDF files are not fetched or rehosted.

This tool does not claim an XBRL presentation/calculation hierarchy. Use get_dart_financials for normalized figures, reported account groups and known statement sum checks.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`entry`	No	Archive entry to explore, exactly as the overview's entries list names it (e.g. 20260313001021_00761.xml for a consolidated audit report). Omit for the main body. Attachments are read from DART, not from the preserved copy.
`fresh`	No	false (default): read FinBridge's preserved copy of this filing when we hold one, and DART otherwise. true: fetch the current version from DART now — use only when the user asks for the latest text or suspects a correction.
`action`	No	Start with the outline, then select a section or a leaf table.	overview
`max_rows`	No	Maximum selected table rows; original row count is retained.
`rcept_no`	Yes	14-digit DART receipt number from get_dart_filings
`max_chars`	No	Maximum characters of selected section text; truncation is explicit.
`max_columns`	No	Maximum selected table columns; original column count is retained.
`table_index`	No	1-based leaf-table number; required for table action.
`compare_index`	No	Table or section index inside the second filing. Read that filing's overview first; table_index/section_index selects the first filing's side.
`section_index`	No	1-based section number from the outline; use only with section action.
`section_query`	No	Section title search; use instead of section_index. Ambiguous matches are rejected.
`overview_limit`	No	Maximum section and table summaries per outline page; follow next_offset.
`overview_offset`	No	0-based outline slice offset for both sections and tables.
`response_format`	No	Readable markdown or JSON; both retain structured content.	markdown
`compare_rcept_no`	No	Second filing's 14-digit receipt number, for compare_tables / compare_sections. The first filing is rcept_no.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`notes`	No
`table`	No
`action`	Yes
`tables`	No
`section`	No
`overview`	No
`sections`	No
`comparison`	No
`preservation`	No
`source_evidence`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 1, 2026
- addedInput schema / properties / entry / maxLength
```
Added value: +120
```
- addedInput schema / properties / entry / minLength
```
Added value: +1
```
- removedInput schema / properties / entry / pattern
```
Removed value: -"^[\\p{L}\\p{N}._/-]{1,120}$"
```

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / entry

Added value: +{
+  "description": "Archive entry to explore, exactly as the overview's entries list names it (e.g. 20260313001021_00761.xml for a consolidated audit report). Omit for the main body. Attachments are read from DART, not from the preserved copy.",
+  "pattern": "^[\\p{L}\\p{N}._/-]{1,120}$",
+  "type": "string"
+}

Changed1 schema field changedSep 25, 2026

addedInput schema / properties / fresh

Added value: +{
+  "default": false,
+  "description": "false (default): read FinBridge's preserved copy of this filing when we hold one, and DART otherwise. true: fetch the current version from DART now — use only when the user asks for the latest text or suspects a correction.",
+  "type": "boolean"
+}

Changed2 schema fields changedSep 23, 2026

addedInput schema / properties / compare_index / description

Added value: +"Table or section index inside the second filing. Read that filing's overview first; table_index/section_index selects the first filing's side."

addedInput schema / properties / compare_rcept_no / description

Added value: +"Second filing's 14-digit receipt number, for compare_tables / compare_sections. The first filing is rcept_no."

Changed6 schema fields changedSep 9, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "overview",
-  "section",
-  "table"
-]New value: +[
+  "overview",
+  "section",
+  "table",
+  "compare_tables",
+  "compare_sections"
+]

addedInput schema / properties / compare_index

Added value: +{
+  "exclusiveMinimum": 0,
+  "maximum": 10000,
+  "type": "integer"
+}

addedInput schema / properties / compare_rcept_no

Added value: +{
+  "pattern": "^\\d{14}$",
+  "type": "string"
+}

changedOutput schema / properties / action / enum

Previous value: -[
-  "overview",
-  "section",
-  "table"
-]New value: +[
+  "overview",
+  "section",
+  "table",
+  "compare_tables",
+  "compare_sections"
+]

addedOutput schema / properties / comparison

Added value: +{
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

addedOutput schema / properties / preservation

Added value: +{
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

AddedSep 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare read-only/destructive=false, but the description adds real behavioral context beyond them: preserved-copy vs live-DART reads (fresh), table structure retention (row/col order, span, unit labels), that zero/negative strings survive, and the explicit disclaimer that no XBRL hierarchy is claimed.

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 with purpose and routing before the arg list, and every section carries information. The args block largely restates schema fields, which is mild redundancy rather than waste; overall it is long but well organized.

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 15-parameter, multi-action tool with an output schema and annotations, the description covers workflow ordering, comparison semantics, truncation/pagination behavior, and explicit non-goals. An agent has everything needed to call it correctly.

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 coverage is 100% so per-parameter meaning is already documented; the description still adds interaction-level semantics the schema lacks — that compare_rcept_no compares only the selected table/section, that both overviews must be read first, and that section_query rejects ambiguous matches.

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 ('Explore one DART filing by receipt number') and immediately scopes it: main body by default or a named attachment. It also names the sibling it is not (get_dart_financials for normalized figures), so an agent can route correctly without opening schemas.

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?

Explicit sequencing: 'Use get_dart_filings first to obtain rcept_no', 'Start with action=overview', then select a section/table rather than requesting a flattened filing. It also names the alternative tool for normalized figures and the condition selecting it, plus the HWP/PDF exclusion.

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

All FinBridge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.