Skip to main content
Glama

Track Korean DART filings

track_korean_filings
Read-onlyIdempotent

Retrieve recent Korean DART filings for KOSPI/KOSDAQ/KONEX/KRX companies. Supports periodic reports, major events, issuance, shareholding, audit, and more.

Instructions

Korean DART (전자공시) filings retrieval for KOSPI / KOSDAQ / KONEX / KRX listed companies — 5%-rule disclosures, M&A, periodic reports, capital issuance, insider trading, audit reports. Free tier.

Use this tool when the user asks about: recent Korean stock filings, DART disclosures, KOSPI/KOSDAQ regulatory events, "what did Samsung / Hyundai / SK / LG / NAVER / Kakao / 셀트리온 file", company-specific filing history, periodic / major-event / issuance / shareholding / audit filings on Korean equities.

Free tier — no license required. Returns raw DART filings exactly as the regulator surfaces them (filer name in Korean, filing type code, receipt number, optional EN translation of the title).

Important for LLM clients — read this before retrying after a paid- tool license error. This tool returns raw filings only. It does NOT classify the filer. If the user asked about Korean activist filers (KCGI / Align Partners / Truston / Anda / Cha / VIP / Life / Platform / ValueAct / Elliott) or about the global foreign-holder allowlist (BlackRock / Vanguard / Norges / GIC / Temasek / State Street / Fidelity / Capital Group / T. Rowe Price / Wellington / Goldman / JPMorgan / Morgan Stanley / Citadel / Millennium / Bridgewater + others), the matching work happens in monitor_activist_investors and monitor_foreign_holders — both require a license_key argument. A response from this free tool to a "are activists filing on X?" or "is BlackRock holding X?" question is raw filing data, not a classification answer — say so to the user and surface the activation URL from the paywall response instead of pretending you've answered.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_corp_codeNo8-digit DART corp code. Use `lookup_corp_code` first to resolve a company name. Omit to query all companies.
daysNohow many days back from today (1–30).
filing_typeNooptional one-letter code: A=periodic, B=major event, C=issuance, D=shareholding, E=other, F=audit, G=fund, H=ABS, I=exchange, J=FTC.
limitNomax filings to return (≤100). DART returns most-recent first, so on a busy window the older end of the range is dropped first. Narrow `days` or `filing_type` if you need older items.
translateNoTrue to fill `title_en` via server-side LLM (cached).
summarizeNoTrue to fill `summary_en` (≤200 words). Costs more — use sparingly. Long-form analysis should be done by the client LLM.
license_keyNosubscription key. Required when KOREANPULSE_REQUIRE_LICENSE=1.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds significant behavioral context: it returns raw filings without classification, does not require a license for free tier, and explicitly warns about paywall activation for paid tools. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy (multiple paragraphs) and includes repetitive warnings. While front-loaded with purpose, it lacks conciseness. It is structured but could be more efficient.

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 (multiple parameters, sibling tools, and an output schema), the description is thorough. It covers purpose, usage, limitations, and links to other tools. Output schema exists, so return values are handled separately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with all parameters described. The description does not add substantial parameter details beyond the schema, but it does provide high-level context about the license_key and free tier. Baseline 3 is appropriate.

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 clearly states it retrieves Korean DART filings for KOSPI/KOSDAQ/KONEX/KRX companies, listing specific filing types. It distinguishes from siblings like monitor_activist_investors and monitor_foreign_holders by explicitly stating when to use each.

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 description explicitly provides usage scenarios ('Use this tool when...') and warns against using it for activist or foreign holder queries, directing users to alternative tools. It also explains that the free tier provides raw data without classification.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/whdrnr2583-cmd/koreanpulse'

If you have feedback or need assistance with the MCP directory API, please join our Discord server