Skip to main content
Glama

search_disclosures

Read-only

MyDART MCP의 search_disclosures 도구는 DART 공시 목록에서 접수번호(rcept_no)를 찾습니다 — download_document·get_attachments 진입점.

[Purpose]

  • 사업보고서 섹션 데이터는 get_periodic_report, 동명 회사는 find_corp_code 로 corp_code 확정.

[Usage]

  1. "삼성전자 최근 한 달 공시" → corp="삼성전자", days=30

  2. "작년 유상증자 결정 전부" → preset="rights_offering", start="2025-01-01", end="2025-12-31"

[Response]

  • corp_cls: Y=코스피, K=코스닥, N=코넥스, E=기타(비상장).

  • report_nm [기재정정]/[첨부정정]/[첨부추가] prefix = 정정공시.

[Rules]

  • Always pass corp when a company is named — corp-less searches (page mode too) split into 90-day chunks, batch request budget 60; with corp: 1 request.

  • Counters nest: total_available ≥ total_fetched ≥ matched ≥ returned; matched > returned = cut by limit, incomplete=true = partial (see incomplete_note). collected_periods = the only ranges queried; counters scope to them, the rest is unchecked, not zero.

  • early_stopped:true = limit filled, rest unfetched — matched is a lower bound.

  • Preset batch drops 정정공시; page mode·bare all_pages keep them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoEnd date (defaults to today)
corpNo회사명/종목코드/corp_code. Omit for all companies — but a batch without corp splits the period into 90-day chunks and sweeps every company, spending up to the per-call request budget (default 60, env SEARCH_MAX_REQUESTS) and taking tens of seconds; on reaching it collection is truncated and flagged incomplete=true. With corp the split disappears and the same query finishes in 1 request and a few hundred ms.
daysNoTrailing N days from today instead of start (1~730; out-of-range values are clamped to the bound). When unset, the preset default applies: 사업·감사 460 / 반기 280 / 분기 180 / 수시·일반 90. For windows longer than 730 days use start/end
kindNo공시유형: periodic/major/issuance/holdings/audit/other/fund/abs/exchange/ftc
pageNoPage number (page mode — the default when neither preset nor all_pages is set). Row shape differs by mode: page mode items are raw DART list rows, batch mode items a 7-key projection (rcept_no·rcept_dt·corp_name·corp_code·corp_cls·report_nm·flr_nm), so any field outside those 7 is only in page mode.
sizeNoPage size (page mode)
limitNoCap on rows finally returned in batch mode (preset given or all_pages=true)
startNoStart date YYYY-MM-DD. When omitted, `days` back from today (and when that is unset, the preset default: 사업·감사 460 / 반기 280 / 분기 180 / 수시·일반 90) — set it explicitly for older filings. (The old parameter name begin is still accepted — unified with start/end in get_corporate_event.)
presetNo22 presets: treasury_buy/sell/trust · cb/bw/eb_issue · rights_offering/bonus_issue/capital_reduction · merger/split/stock_exchange · business_transfer/acquisition · large_holding_5pct · annual_report/half_report/quarterly_report · audit_report · correction_all · insolvency · litigation. Setting one applies kind and a keyword filter automatically and collects every page in parallel.
all_pagesNoCollect the whole period in parallel even without a preset (정정공시 included — the same set as page mode). When true, limit applies instead of page/size.
final_onlyNoOne latest version per event — where a 정정 exists the 구본(원본) is dropped and the latest 정정본 is taken (this does NOT exclude 정정공시 themselves). Use when you need one duplicate-free set.
concurrencyNoCollector workers in batch mode (1~10, default 5). **Effective concurrency is set by a server-wide cap, so raising this usually does NOT make it faster** — to cut latency, set corp (which removes the period split, leaving a single request), narrow the period, or lower limit. The response's dart_requests/cached_chunks report how many DART requests this call spent and how many chunks came from cache — read them when it feels slow.
include_correctionsNoWhether to include 정정공시 ([기재정정] etc.) — preset batch mode ONLY (default false, to avoid double-counting 원본+정정 of the same event; correction_all forces true; ignored when final_only=true since that already removes duplicates). Bare all_pages and page mode ALWAYS include them (raw DART) — for latest-only without duplicates use final_only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / corp / description
      Previous value: -"회사명/종목코드/corp_code. Omit for all companies — but a batch without corp splits the period into 90-day chunks and sweeps every company, so DART requests grow to tens~150 and it takes tens of seconds. With corp the split disappears and the same query finishes in 1 request and a few hundred ms (152× measured)."New value: +"회사명/종목코드/corp_code. Omit for all companies — but a batch without corp splits the period into 90-day chunks and sweeps every company, spending up to the per-call request budget (default 60, env SEARCH_MAX_REQUESTS) and taking tens of seconds; on reaching it collection is truncated and flagged incomplete=true. With corp the split disappears and the same query finishes in 1 request and a few hundred ms."
  2. Changed5 schema fields changed
    • changedInput schema / properties / concurrency / description
      Previous value: -"Collector workers in batch mode (1~10, default 5). **Effective concurrency is set by a server-wide cap, so raising this usually does NOT make it faster** — to cut latency, set corp (which removes the period split, leaving a single request), narrow the period, or lower limit."New value: +"Collector workers in batch mode (1~10, default 5). **Effective concurrency is set by a server-wide cap, so raising this usually does NOT make it faster** — to cut latency, set corp (which removes the period split, leaving a single request), narrow the period, or lower limit. The response's dart_requests/cached_chunks report how many DART requests this call spent and how many chunks came from cache — read them when it feels slow."
    • changedInput schema / properties / corp / description
      Previous value: -"회사명/종목코드/corp_code. Omit for all companies"New value: +"회사명/종목코드/corp_code. Omit for all companies — but a batch without corp splits the period into 90-day chunks and sweeps every company, so DART requests grow to tens~150 and it takes tens of seconds. With corp the split disappears and the same query finishes in 1 request and a few hundred ms (152× measured)."
    • changedInput schema / properties / limit / description
      Previous value: -"Cap on rows finally returned (batch mode)"New value: +"Cap on rows finally returned in batch mode (preset given or all_pages=true)"
    • changedInput schema / properties / page / description
      Previous value: -"Page number (page mode)"New value: +"Page number (page mode — the default when neither preset nor all_pages is set). Row shape differs by mode: page mode items are raw DART list rows, batch mode items a 7-key projection (rcept_no·rcept_dt·corp_name·corp_code·corp_cls·report_nm·flr_nm), so any field outside those 7 is only in page mode."
    • changedInput schema / properties / start / description
      Previous value: -"Start date YYYY-MM-DD. When omitted, `days` back from today (and when that is unset, the preset default: 사업·감사 460 / 반기 280 / 분기 180 / 수시·일반 90). (The old parameter name begin is still accepted — unified with start/end in get_corporate_event.)"New value: +"Start date YYYY-MM-DD. When omitted, `days` back from today (and when that is unset, the preset default: 사업·감사 460 / 반기 280 / 분기 180 / 수시·일반 90) — set it explicitly for older filings. (The old parameter name begin is still accepted — unified with start/end in get_corporate_event.)"
  3. Changed12 schema fields changed
    • changedInput schema / properties / all_pages / description
      Previous value: -"preset 없이도 기간 전체를 병렬 수집(정정공시 포함 — 페이지 모드와 동일 집합). true 시 page/size 대신 limit 적용."New value: +"Collect the whole period in parallel even without a preset (정정공시 included — the same set as page mode). When true, limit applies instead of page/size."
    • changedInput schema / properties / concurrency / description
      Previous value: -"배치 모드 수집 워커 수(1~10, 기본 5). **실효 동시성은 서버 전역 상한이 정하므로 이 값을 올려도 대개 빨라지지 않는다** — 지연을 줄이려면 corp 지정(기간 분할이 사라져 요청 1건)·기간 축소·limit 축소가 효과적이다."New value: +"Collector workers in batch mode (1~10, default 5). **Effective concurrency is set by a server-wide cap, so raising this usually does NOT make it faster** — to cut latency, set corp (which removes the period split, leaving a single request), narrow the period, or lower limit."
    • changedInput schema / properties / corp / description
      Previous value: -"회사명/종목코드/corp_code. 생략 시 전체"New value: +"회사명/종목코드/corp_code. Omit for all companies"
    • changedInput schema / properties / days / description
      Previous value: -"start 대신 오늘 기준 과거 N일(1~730, 벗어나면 경계로 보정). 미지정 시 preset별 기본: 사업·감사 460·반기 280·분기 180·수시/일반 90. 730일보다 긴 기간은 start/end 로 지정하세요"New value: +"Trailing N days from today instead of start (1~730; out-of-range values are clamped to the bound). When unset, the preset default applies: 사업·감사 460 / 반기 280 / 분기 180 / 수시·일반 90. For windows longer than 730 days use start/end"
    • changedInput schema / properties / end / description
      Previous value: -"종료일 (생략 시 오늘)"New value: +"End date (defaults to today)"
    • changedInput schema / properties / final_only / description
      Previous value: -"이벤트당 최신본 1본만 — 정정이 있으면 구본(원본)을 빼고 최신 정정본을 채택한다(정정공시 자체를 제외하는 게 아님). 중복 없는 한 벌이 필요할 때 사용."New value: +"One latest version per event — where a 정정 exists the 구본(원본) is dropped and the latest 정정본 is taken (this does NOT exclude 정정공시 themselves). Use when you need one duplicate-free set."
    • changedInput schema / properties / include_corrections / description
      Previous value: -"정정공시([기재정정] 등) 포함 여부 — preset 배치 모드 전용(기본 false: 같은 이벤트의 원본+정정 중복 집계 방지, correction_all 은 자동 true, final_only=true 면 이미 중복이 없어 무시). preset 없는 all_pages·페이지 모드는 항상 포함(DART 원본 그대로) — 중복 없이 최신본만 원하면 final_only."New value: +"Whether to include 정정공시 ([기재정정] etc.) — preset batch mode ONLY (default false, to avoid double-counting 원본+정정 of the same event; correction_all forces true; ignored when final_only=true since that already removes duplicates). Bare all_pages and page mode ALWAYS include them (raw DART) — for latest-only without duplicates use final_only."
    • changedInput schema / properties / limit / description
      Previous value: -"배치 모드 최종 반환 개수 상한"New value: +"Cap on rows finally returned (batch mode)"
    • changedInput schema / properties / page / description
      Previous value: -"페이지 모드 시 페이지 번호"New value: +"Page number (page mode)"
    • changedInput schema / properties / preset / description
      Previous value: -"프리셋 22종: treasury_buy/sell/trust · cb/bw/eb_issue · rights_offering/bonus_issue/capital_reduction · merger/split/stock_exchange · business_transfer/acquisition · large_holding_5pct · annual_report/half_report/quarterly_report · audit_report · correction_all · insolvency · litigation. 지정 시 kind·키워드 자동 + 전량 페이지 병렬 수집."New value: +"22 presets: treasury_buy/sell/trust · cb/bw/eb_issue · rights_offering/bonus_issue/capital_reduction · merger/split/stock_exchange · business_transfer/acquisition · large_holding_5pct · annual_report/half_report/quarterly_report · audit_report · correction_all · insolvency · litigation. Setting one applies kind and a keyword filter automatically and collects every page in parallel."
    • changedInput schema / properties / size / description
      Previous value: -"페이지 모드 시 페이지 크기"New value: +"Page size (page mode)"
    • changedInput schema / properties / start / description
      Previous value: -"시작일 YYYY-MM-DD. 생략 시 days(미지정이면 preset별 기본: 사업·감사 460·반기 280·분기 180·수시/일반 90)일 전. (구 파라미터명 begin 도 허용 — get_major_holdings·get_corporate_event 의 start/end 와 통일)"New value: +"Start date YYYY-MM-DD. When omitted, `days` back from today (and when that is unset, the preset default: 사업·감사 460 / 반기 280 / 분기 180 / 수시·일반 90). (The old parameter name begin is still accepted — unified with start/end in get_corporate_event.)"
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark the tool read-only and non-destructive, so the description goes beyond them by disclosing batch behavior, 90-day chunking, the request budget of 60, counter nesting semantics, early_stopped implications, and correction-disclosure handling. This is rich behavioral context that materially affects how an agent interprets results.

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

Conciseness5/5

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

The description is long but highly structured with Purpose, Usage, Response, and Rules sections, each earning its place. For a tool with 13 optional parameters and subtle batch-mode behaviors, the density is justified and the most critical operational rules are front-loaded.

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?

With no output schema, the description still explains the response codes (corp_cls, report_nm correction prefixes) and the exact meaning of counters like total_available, matched, returned, incomplete, and early_stopped. It covers the non-obvious result-interpretation traps an agent would otherwise miss, making the definition complete for correct invocation and result understanding.

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 description coverage is 100%, so the baseline is 3; the schema already documents each parameter in detail. The tool description adds usage examples for corp/days/preset/start/end and stresses the corp parameter's performance implications, but it does not substantially define parameters beyond what the schema already provides.

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 precise job: find rcept_no in the DART disclosure list and serve as the entry point to download_document/get_attachments. It also distinguishes itself from get_periodic_report and find_corp_code, so an agent can tell it apart from siblings without opening schemas.

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 explicitly routes business-report section data to get_periodic_report and same-name company resolution to find_corp_code, giving clear when-not-to-use guidance. The [Usage] examples translate natural-language requests into concrete parameter choices, and the [Rules] section adds operational conditions such as always passing corp when a company is named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources