MyDART

by kr.eocpa

Overview Discussions Admin

get_corporate_event

Read-only

MyDART MCP의 get_corporate_event 도구는 주요사항보고서 자본·지배구조 이벤트 36종(증자·감자·CB/BW/EB·자기주식·합병/분할 등)과 5%룰·임원 지분공시를 조회합니다.

[Purpose]

"Who raised/cut stakes, when": event_type="holdings" (5%룰 대량보유·임원/주요주주 소유보고).
결정의 후속 발행·합병 조건(공모가·인수인): get_registration_statement.
List skims: search_disclosures; 사업보고서 snapshots (최대주주·주식총수): get_periodic_report.

[Usage]

"카카오 최근 3년 자본 조달 흐름" → corp="카카오", mode="timeline"
"이 회사 CB 발행한 적 있어?" → corp="…", event_type="cb_issuance"
"자사주 취득·처분 2020년부터" → event_type=["treasury_acquisition","treasury_disposal"], start="2020-01-01"

[Response]

date = 최초 공시일 (start/end axis), newest first; fields = latest 정정본 (rcept_no) — corrected: last_filed_date.
지분공시: total_count = all-time cumulative, filtered_count = in-period (DART takes no dates — filtered client-side).

[Rules]

Empty timeline ≠ no events — default set = capital events only (name event_type for more); sections_meta may carry per-endpoint errors.
event_type_counts is pre-truncation (limit cuts timeline only).

Input Schema

Name	Required	Description	Default
`end`	No	YYYY-MM-DD / YYYYMMDD; default today (period.end_defaulted:true)
`corp`	Yes	회사명/종목코드/corp_code
`mode`	No	single: one event_type. timeline: several event_types (unset → 'capital' group) in parallel, merged into one newest-first list	single
`limit`	No	Max timeline rows, newest first by 최초 공시일. Excess cut → truncated=true, total_events = full count. Prefer narrowing start/end over raising limit.
`start`	No	YYYY-MM-DD / YYYYMMDD; default 3 years ago (period.defaulted:true). start/end match each event's first filing (DART 최초접수일) — an in-window 정정 of an event first filed earlier is not returned
`event_type`	No	String = one event (mode=single); array = several merged into one timeline (mode auto-switches to timeline). Unset in timeline = 'capital' group only (자본거래 25종). Group aliases: 'capital', 'holdings' (지분공시 2종).

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 15, 2026

changedInput schema / properties / end / description

Previous value: -"End date (YYYY-MM-DD / YYYYMMDD). Defaults to today — omitted end is flagged as period.end_defaulted:true"New value: +"YYYY-MM-DD / YYYYMMDD; default today (period.end_defaulted:true)"

changedInput schema / properties / event_type / description

Previous value: -"38 selectable events (36 주요사항 + 지분공시 2종) — **a single string OR an array**. A string queries that one event (mode=single); an array queries them in parallel and merges them into one date-descending timeline (mode switches to timeline automatically). When unset in timeline mode, every 자본 관련 event (capital=true) is selected; 소송·부도·회생·해외상장·지분공시 are NOT in that default set, so name them here. Group aliases expand to their members — 'capital' (자본거래 25종, the timeline default) and 'holdings' (지분공시 2종). The legacy key `event_types` is accepted."New value: +"String = one event (mode=single); array = several merged into one timeline (mode auto-switches to timeline). Unset in timeline = 'capital' group only (자본거래 25종). Group aliases: 'capital', 'holdings' (지분공시 2종)."

changedInput schema / properties / limit / description

Previous value: -"Cap on timeline rows returned (default 100, date descending — 최초 공시일). The excess is cut and flagged via truncated=true, with total_events carrying the real count — a company with frequent 자본거래 yields hundreds over a 3-year window. Narrowing the period is more precise."New value: +"Max timeline rows, newest first by 최초 공시일. Excess cut → truncated=true, total_events = full count. Prefer narrowing start/end over raising limit."

changedInput schema / properties / mode / description

Previous value: -"single: query one event_type. timeline: query the 자본 관련 events in parallel (25 types by default) and merge them into one date-descending list"New value: +"single: one event_type. timeline: several event_types (unset → 'capital' group) in parallel, merged into one newest-first list"

changedInput schema / properties / start / description

Previous value: -"Start date (YYYY-MM-DD / YYYYMMDD). Defaults to 3 years ago — omitted start is flagged as period.defaulted:true. start/end match each event's FIRST filing (DART 최초접수일) — a 정정 filed in the window for an event first filed earlier is not returned"New value: +"YYYY-MM-DD / YYYYMMDD; default 3 years ago (period.defaulted:true). start/end match each event's first filing (DART 최초접수일) — an in-window 정정 of an event first filed earlier is not returned"

Changed3 schema fields changedOct 7, 2026

changedInput schema / properties / end / description

Previous value: -"End date (YYYY-MM-DD / YYYYMMDD). Defaults to today"New value: +"End date (YYYY-MM-DD / YYYYMMDD). Defaults to today — omitted end is flagged as period.end_defaulted:true"

changedInput schema / properties / limit / description

Previous value: -"Cap on timeline rows returned (default 100, date descending). The excess is cut and flagged via truncated=true, with total_events carrying the real count — a company with frequent 자본거래 yields hundreds over a 3-year window. Narrowing the period is more precise."New value: +"Cap on timeline rows returned (default 100, date descending — 최초 공시일). The excess is cut and flagged via truncated=true, with total_events carrying the real count — a company with frequent 자본거래 yields hundreds over a 3-year window. Narrowing the period is more precise."

changedInput schema / properties / start / description

Previous value: -"Start date (YYYY-MM-DD / YYYYMMDD). Defaults to 3 years ago — an omitted bound is flagged as period.defaulted:true in the response"New value: +"Start date (YYYY-MM-DD / YYYYMMDD). Defaults to 3 years ago — omitted start is flagged as period.defaulted:true. start/end match each event's FIRST filing (DART 최초접수일) — a 정정 filed in the window for an event first filed earlier is not returned"

Changed5 schema fields changedSep 2, 2026

addedInput schema / properties / event_type / anyOf

Added value: +[
+  {
+    "enum": [
+      "major_holding_5pct",
+      "executive_holding",
+      "default_occurrence",
+      "business_suspension",
+      "rehabilitation_filing",
+      "dissolution_cause",
+      "bank_management_start",
+      "bank_management_stop",
+      "litigation",
+      "rights_offering",
+      "bonus_issue",
+      "rights_bonus_combo",
+      "capital_reduction",
+      "cb_issuance",
+      "bw_issuance",
+      "eb_issuance",
+      "cocobond_issuance",
+      "treasury_acquisition",
+      "treasury_disposal",
+      "treasury_trust_contract",
+      "treasury_trust_cancel",
+      "stock_exchange",
+      "company_split_merger",
+      "company_split",
+      "company_merger",
+      "asset_transfer_etc",
+      "tangible_asset_transfer",
+      "tangible_asset_acquisition",
+      "other_corp_stock_transfer",
+      "other_corp_stock_acquisition",
+      "business_transfer",
+      "business_acquisition",
+      "bond_with_stock_right_acquisition",
+      "bond_with_stock_right_transfer",
+      "overseas_listing_decision",
+      "overseas_delisting_decision",
+      "overseas_listing",
+      "overseas_delisting"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "major_holding_5pct",
+        "executive_holding",
+        "default_occurrence",
+        "business_suspension",
+        "rehabilitation_filing",
+        "dissolution_cause",
+        "bank_management_start",
+        "bank_management_stop",
+        "litigation",
+        "rights_offering",
+        "bonus_issue",
+        "rights_bonus_combo",
+        "capital_reduction",
+        "cb_issuance",
+        "bw_issuance",
+        "eb_issuance",
+        "cocobond_issuance",
+        "treasury_acquisition",
+        "treasury_disposal",
+        "treasury_trust_contract",
+        "treasury_trust_cancel",
+        "stock_exchange",
+        "company_split_merger",
+        "company_split",
+        "company_merger",
+        "asset_transfer_etc",
+        "tangible_asset_transfer",
+        "tangible_asset_acquisition",
+        "other_corp_stock_transfer",
+        "other_corp_stock_acquisition",
+        "business_transfer",
+        "business_acquisition",
+        "bond_with_stock_right_acquisition",
+        "bond_with_stock_right_transfer",
+        "overseas_listing_decision",
+        "overseas_delisting_decision",
+        "overseas_listing",
+        "overseas_delisting"
+      ],
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  }
+]

changedInput schema / properties / event_type / description

Previous value: -"REQUIRED in single mode. One of the 38 selectable events (36 주요사항 + 지분공시 2종)"New value: +"38 selectable events (36 주요사항 + 지분공시 2종) — **a single string OR an array**. A string queries that one event (mode=single); an array queries them in parallel and merges them into one date-descending timeline (mode switches to timeline automatically). When unset in timeline mode, every 자본 관련 event (capital=true) is selected; 소송·부도·회생·해외상장·지분공시 are NOT in that default set, so name them here. Group aliases expand to their members — 'capital' (자본거래 25종, the timeline default) and 'holdings' (지분공시 2종). The legacy key `event_types` is accepted."

removedInput schema / properties / event_type / enum

Removed value: -[
-  "major_holding_5pct",
-  "executive_holding",
-  "default_occurrence",
-  "business_suspension",
-  "rehabilitation_filing",
-  "dissolution_cause",
-  "bank_management_start",
-  "bank_management_stop",
-  "litigation",
-  "rights_offering",
-  "bonus_issue",
-  "rights_bonus_combo",
-  "capital_reduction",
-  "cb_issuance",
-  "bw_issuance",
-  "eb_issuance",
-  "cocobond_issuance",
-  "treasury_acquisition",
-  "treasury_disposal",
-  "treasury_trust_contract",
-  "treasury_trust_cancel",
-  "stock_exchange",
-  "company_split_merger",
-  "company_split",
-  "company_merger",
-  "asset_transfer_etc",
-  "tangible_asset_transfer",
-  "tangible_asset_acquisition",
-  "other_corp_stock_transfer",
-  "other_corp_stock_acquisition",
-  "business_transfer",
-  "business_acquisition",
-  "bond_with_stock_right_acquisition",
-  "bond_with_stock_right_transfer",
-  "overseas_listing_decision",
-  "overseas_delisting_decision",
-  "overseas_listing",
-  "overseas_delisting"
-]

removedInput schema / properties / event_type / type
```
Removed value: -"string"
```

removedInput schema / properties / event_types

Removed value: -{
-  "description": "Manual selection for timeline mode — passing this switches mode to timeline automatically. When unset, every 자본 관련 event (capital=true) is selected; 소송·부도·회생·해외상장·지분공시 are NOT in that default set, so request them explicitly here. Group aliases are accepted too — 'capital' (자본거래 25종, the timeline default) and 'holdings' (지분공시 2종)",
-  "items": {
-    "enum": [
-      "major_holding_5pct",
-      "executive_holding",
-      "default_occurrence",
-      "business_suspension",
-      "rehabilitation_filing",
-      "dissolution_cause",
-      "bank_management_start",
-      "bank_management_stop",
-      "litigation",
-      "rights_offering",
-      "bonus_issue",
-      "rights_bonus_combo",
-      "capital_reduction",
-      "cb_issuance",
-      "bw_issuance",
-      "eb_issuance",
-      "cocobond_issuance",
-      "treasury_acquisition",
-      "treasury_disposal",
-      "treasury_trust_contract",
-      "treasury_trust_cancel",
-      "stock_exchange",
-      "company_split_merger",
-      "company_split",
-      "company_merger",
-      "asset_transfer_etc",
-      "tangible_asset_transfer",
-      "tangible_asset_acquisition",
-      "other_corp_stock_transfer",
-      "other_corp_stock_acquisition",
-      "business_transfer",
-      "business_acquisition",
-      "bond_with_stock_right_acquisition",
-      "bond_with_stock_right_transfer",
-      "overseas_listing_decision",
-      "overseas_delisting_decision",
-      "overseas_listing",
-      "overseas_delisting"
-    ],
-    "type": "string"
-  },
-  "type": "array"
-}

Changed4 schema fields changedAug 14, 2026

changedInput schema / properties / event_types / description

Previous value: -"Manual selection for timeline mode. When unset, every 자본 관련 event (capital=true) is selected automatically"New value: +"Manual selection for timeline mode — passing this switches mode to timeline automatically. When unset, every 자본 관련 event (capital=true) is selected; 소송·부도·회생·해외상장·지분공시 are NOT in that default set, so request them explicitly here. Group aliases are accepted too — 'capital' (자본거래 25종, the timeline default) and 'holdings' (지분공시 2종)"

changedInput schema / properties / limit / description

Previous value: -"Cap on timeline rows returned (default 100, date descending). The excess is cut and flagged via truncated/total_events — a company with frequent 자본거래 yields hundreds over a 3-year window. Narrowing the period is more precise."New value: +"Cap on timeline rows returned (default 100, date descending). The excess is cut and flagged via truncated=true, with total_events carrying the real count — a company with frequent 자본거래 yields hundreds over a 3-year window. Narrowing the period is more precise."

changedInput schema / properties / mode / description

Previous value: -"single: query one event_type. timeline: merge several 자본 관련 events in date order"New value: +"single: query one event_type. timeline: query the 자본 관련 events in parallel (25 types by default) and merge them into one date-descending list"

changedInput schema / properties / start / description

Previous value: -"Start date (YYYY-MM-DD / YYYYMMDD). Defaults to 3 years ago"New value: +"Start date (YYYY-MM-DD / YYYYMMDD). Defaults to 3 years ago — an omitted bound is flagged as period.defaulted:true in the response"

Changed6 schema fields changedAug 13, 2026

changedInput schema / properties / end / description

Previous value: -"종료일 (YYYY-MM-DD / YYYYMMDD). 미지정 시 오늘"New value: +"End date (YYYY-MM-DD / YYYYMMDD). Defaults to today"

changedInput schema / properties / event_type / description

Previous value: -"single 모드 필수. 36개 이벤트 중 하나"New value: +"REQUIRED in single mode. One of the 38 selectable events (36 주요사항 + 지분공시 2종)"

changedInput schema / properties / event_types / description

Previous value: -"timeline 모드용 수동 선택. 미지정 시 자본 관련 이벤트(capital=true) 전체 자동 선택"New value: +"Manual selection for timeline mode. When unset, every 자본 관련 event (capital=true) is selected automatically"

changedInput schema / properties / limit / description

Previous value: -"timeline 반환 건수 상한(기본 100, 날짜 내림차순). 초과분은 잘리고 truncated/total_events 로 표기됩니다 — 자본거래가 잦은 회사는 3년 창에서 수백 건이 나옵니다. 기간을 좁히는 편이 더 정확합니다."New value: +"Cap on timeline rows returned (default 100, date descending). The excess is cut and flagged via truncated/total_events — a company with frequent 자본거래 yields hundreds over a 3-year window. Narrowing the period is more precise."

changedInput schema / properties / mode / description

Previous value: -"single: 단일 event_type 조회. timeline: 여러 자본 관련 이벤트를 날짜순 통합"New value: +"single: query one event_type. timeline: merge several 자본 관련 events in date order"

changedInput schema / properties / start / description

Previous value: -"시작일 (YYYY-MM-DD / YYYYMMDD). 미지정 시 3년 전"New value: +"Start date (YYYY-MM-DD / YYYYMMDD). Defaults to 3 years ago"

First observedAug 13, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, non-destructive, openWorld), and the description adds substantial context beyond them: date axis is 최초 공시일 newest-first, fields come from the latest 정정본, total_count is all-time cumulative while filtered_count is client-side filtered because DART takes no dates, empty timeline ≠ no events, and event_type_counts is pre-truncation. This is exactly the extra behavioral layer annotations cannot supply.

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?

Dense but well-sectioned ([Purpose]/[Usage]/[Response]/[Rules]) and front-loaded with the one-line purpose before details. Slightly long and a few lines (e.g. the paper-price/investor note) sit close to redundancy, but every block carries operational 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?

No output schema exists, so the description must carry return semantics — and it does, explaining the date axis, correction handling, the two count fields, truncation flags and sections_meta per-endpoint errors. For a 6-param open-world query tool, an agent has everything needed to call it and interpret results.

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 the baseline is 3, but the description adds real meaning on top: mode switching behavior when event_type is an array, the 'capital' default group and 'holdings' alias, the limit-vs-start/end tradeoff guidance, and that start/end match an event's first filing so later 정정 is excluded. These go beyond the schema's own text.

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?

Names a specific resource (주요사항보고서 자본·지배구조 이벤트 36종 plus 5%룰·임원 지분공시) and a clear retrieval verb, then explicitly differentiates from siblings get_registration_statement, search_disclosures and get_periodic_report. An agent can distinguish it from all 14 siblings 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 three concrete usage scenarios keyed to intent ('카카오 최근 3년 자본 조달 흐름', 'CB 발행한 적 있어?', '자사주 취득·처분 2020년부터') and names the alternative tool for each adjacent need. When-to-use and when-to-use-something-else are both explicit.

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

All MyDART 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.

Resources

Need Help?