FinBridge

Korean Major-Event Disclosures (DART)

get_dart_major_events

Read-only

List major-event disclosures (주요사항보고서, DART type B): capital increases, mergers, convertible bonds, treasury stock, bankruptcy, lawsuits, etc. Optionally filter report names with a regex.

Not this tool for: the full disclosure list or other report categories (get_dart_filings — periodic reports, securities issuance, ownership, KRX notices), US 8-K events (get_edgar_filings), or the cross-market stored feed (get_disclosure_feed). What this adds over get_dart_filings type='B': a 'kinds' regex over Korean report names (e.g. '증자|합병|전환사채'), a 180-day default window tuned for event scans, and matched-count totals — so use it when the question is 'which companies announced X', not 'what did company Y file'.

Args:

corp: optional — Company: Korean name (e.g. '삼성전자'), 6-digit stock code (e.g. '005930'), or 8-digit DART corp_code (e.g. '00126380'). Omit for market-wide events.
from / to: YYYY-MM-DD (default: last 180 days)
kinds: optional JavaScript regex matched against the Korean report name, e.g. '증자|합병|전환사채' (capital increase | merger | CB) or '자기주식' (treasury stock). Filtering runs over every event in range when FinBridge's index covers the window, otherwise over the most recent 100 events DART returns.
limit: max results, 1-100 (default 20)

Returns: {total, page, filings: [{rcept_no, corp_name, report_nm, flr_nm, rcept_dt, url}]} — same shape as get_dart_filings. When kinds is given, total = matched count within the scanned window.

Examples:

{corp: '삼성전자', kinds: '자기주식'} -> Samsung treasury-stock decisions in the last 180 days
{kinds: '유상증자', from: '2026-01-01', to: '2026-06-30'} -> market-wide rights offerings in H1 2026

Use when: event-driven screening (rights offerings, mergers, CBs, treasury stock, lawsuits) market-wide or for one company. For every filing category, or when you already know the report you want, use get_dart_filings. Errors: no events in range (DART status 013) -> widen dates; invalid kinds regex; unknown company -> search_dart_company.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	End date YYYY-MM-DD (default: today)
`corp`	No	Optional filter — Company: Korean name (e.g. '삼성전자'), 6-digit stock code (e.g. '005930'), or 8-digit DART corp_code (e.g. '00126380')
`from`	No	Start date YYYY-MM-DD (default: 180 days ago)
`fresh`	No	false (default): answer from FinBridge's DART filings index (refreshed every 5 minutes) for the part of the window it covers, and ask DART live only for the uncovered remainder (saves DART's daily quota). true: ask DART directly for the whole window; on daily-quota exhaustion (020), falls back to the index for whatever it covers and says what could not be refreshed.
`kinds`	No	Regex filter on Korean report names, e.g. '증자\|합병\|전환사채' or '자기주식'
`limit`	No	Max results, 1-100 (default 20)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`page`	No
`total`	No
`filings`	Yes
`sources`	No
`uncovered`	No
`index_as_of`	No
`served_from`	No
`quota_fallback`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 1, 2026

changedInput schema / properties / fresh / description

Previous value: -"false (default): answer from FinBridge's DART filings index (refreshed every 5 minutes) when it covers the window, DART otherwise. true: ask DART directly."New value: +"false (default): answer from FinBridge's DART filings index (refreshed every 5 minutes) for the part of the window it covers, and ask DART live only for the uncovered remainder (saves DART's daily quota). true: ask DART directly for the whole window; on daily-quota exhaustion (020), falls back to the index for whatever it covers and says what could not be refreshed."

addedOutput schema / properties / index_as_of

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / quota_fallback
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / served_from
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / sources

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

addedOutput schema / properties / uncovered

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

Changed1 schema field changedSep 25, 2026

addedInput schema / properties / fresh

Added value: +{
+  "default": false,
+  "description": "false (default): answer from FinBridge's DART filings index (refreshed every 5 minutes) when it covers the window, DART otherwise. true: ask DART directly.",
+  "type": "boolean"
+}

First observedSep 6, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/openWorld/destructive, but the description adds substantial behavior beyond them: the 180-day default scan window, matched-count totals when kinds is set, the index-vs-live-DART scan boundary (FinBridge index vs recent 100 events), quota fallback semantics, and the DART status 013 empty-range error. This is well above the bar set by the annotations.

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 organized into clear labeled sections (Args, Returns, Examples, Use when, Errors), so it scans well. It is on the long side and some of the retroactive-correction phrasing ('What this adds over...') is dense, but essentially every sentence carries decision-relevant information.

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 6-param optional-filter list tool with an output schema, the description covers return shape, defaults, examples, sibling routing, and failure modes. An agent has everything needed to call it correctly and interpret the result without further inference.

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 baseline is 3, but the description adds real meaning: regex examples in Korean for kinds, the corp identifier format variants, and the scanning-window caveat tied to how kinds filtering behaves. It stops short of documenting the 'fresh' parameter, which is left entirely to 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 (List) plus the exact resource (major-event disclosures, DART type B) and enumerates the event types covered. It explicitly distinguishes itself from get_dart_filings, get_edgar_filings, and get_disclosure_feed, so an agent can select it without opening any 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?

Provides an explicit 'Not this tool for' list naming the alternative for each excluded case, a 'What this adds over get_dart_filings type=B' comparison, and a 'Use when' clause with a concrete decision rule ('which companies announced X' vs 'what did company Y file'). When-to-use and when-not-to-use are both fully covered.

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.