FinBridge

Explore Korean Disclosure Document (DART)

get_dart_document

Read-only

Explore the primary body of one DART filing by receipt number while preserving section and table structure.

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.

Args:

rcept_no: 14-digit DART receipt number
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 attachments 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
`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
`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

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.

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?

The description adds substantial behavior beyond the readOnly/openWorld/destructive annotations: preserving table order, rowspan/colspan, unit labels, not discarding zero/negative strings, not fetching HWP/PDF attachments, and explicitly not claiming an XBRL hierarchy. This gives an agent accurate expectations about scope and limitations.

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 description is long, but the tool has 13 parameters and multiple action modes, so the extra length is justified. It is front-loaded with the core purpose and workflow, and the Args section is structured and readable, though some parameter-level detail overlaps with the schema.

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?

Given the tool's complexity, an output schema, and rich annotations, the description is complete: it covers the recommended workflow, comparison flow, truncation/pagination caps, structured-content guarantees, and exclusions. An agent has enough context to invoke it correctly without guessing.

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 high at 85%, but the description adds meaning for the comparison parameters, explaining compare_rcept_no and compare_index as selecting a second filing and index, and advising to use both overviews first. It also clarifies ambiguous section_query rejection and pagination behavior beyond the schema's terse field docs.

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 states a specific verb and resource: 'Explore the primary body of one DART filing by receipt number while preserving section and table structure.' It also differentiates itself from siblings by prescribing get_dart_filings for obtaining the receipt number and get_dart_financials for normalized financial figures, so an agent can tell this tool apart.

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?

Usage guidance is explicit and actionable: '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. It also names the alternative for financial normalization, clarifying when not to use this tool.

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.