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 = filing date (rcept_dt); event dates (이사회 결의일 등) are in raw row fields.
지분공시: 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

TableJSON Schema

Name	Required	Description	Default
`end`	No	End date (YYYY-MM-DD / YYYYMMDD). Defaults to today
`corp`	Yes	회사명/종목코드/corp_code
`mode`	No	single: query one event_type. timeline: query the 자본 관련 events in parallel (25 types by default) and merge them into one date-descending list	single
`limit`	No	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.
`start`	No	Start date (YYYY-MM-DD / YYYYMMDD). Defaults to 3 years ago — an omitted bound is flagged as period.defaulted:true in the response
`event_type`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

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.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, but the description adds significant behavioral context beyond that: date is the filing date while event dates are in raw row fields; holdings counts distinguish all-time cumulative from in-period values; DART accepts no dates and filters client-side; an empty timeline does not mean no events; and event_type_counts is pre-truncation. These are exactly the kind of non-obvious behaviors an agent needs to interpret results correctly.

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 Purpose/Usage/Response/Rules structure front-loads selection guidance and each section contributes non-redundant caveats. Some content overlaps with the already-detailed schema, and the Korean/English mixing adds length, but the density of operational guidance warrants the size.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates well by covering response date semantics, holdings count semantics, per-endpoint error indicators, truncation behavior, and default event-type selection. It does not fully enumerate response shapes for all 38 event types, but for a tool of this complexity the critical invocation and interpretation context is present.

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% and the event_type parameter description is already very rich, including enums, aliases, automatic mode switching, and array behavior. The description adds practical value through usage examples that show valid parameter combinations, such as event_type arrays with start dates, and it clarifies how defaults behave in timeline mode. This justifies slightly above the baseline 3 for fully-schema-documented parameters.

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 opens with a specific verb and resource: it queries 주요사항보고서 capital/governance events (36 types) plus 5% rule and executive equity disclosures. It also explicitly names sibling tools for adjacent use cases, such as get_registration_statement and search_disclosures, so an agent can distinguish this tool from alternatives without inferring.

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?

The Purpose section gives concrete routing rules: for subsequent issuance/merger conditions use get_registration_statement, for list skims use search_disclosures, and for annual report snapshots use get_periodic_report. The Usage section provides three example user intents mapped directly to corp, mode, event_type, and start, making when-to-use guidance explicit rather than implied.

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?