Skip to main content
Glama

search_disclosures

Search Korean DART disclosures using three modes: basic paginated, preset filters for key events, or full parallel retrieval. Supports company, date range, and disclosure type filters.

Instructions

DART 공시 검색 (3 모드): 기본(단일 페이지, page+size), preset(22개 프리셋 자동 필터+전량 병렬), all_pages(프리셋 없이 기간 전체 병렬). rcp_no(rcept_no) 로 download_document / get_attachments 연동.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
corpNo회사명/종목코드/corp_code. 생략 시 전체
beginNo시작일 YYYY-MM-DD (생략 시 기본값)
endNo종료일 (생략 시 오늘)
daysNobegin 대신 오늘 기준 과거 N일 (preset 모드 기본 7, 일반 90)
kindNo공시유형: periodic/major/issuance/holdings/audit/other/fund/abs/exchange/ftc
presetNo프리셋 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·키워드 자동 + 전량 페이지 병렬 수집.
final_onlyNo최종보고서만 (정정공시 제외)
include_correctionsNo정정공시 포함 (preset 모드 전용). correction_all 은 자동 true.
all_pagesNopreset 없이도 기간 전체를 병렬 수집. true 시 page/size 대신 limit 적용.
pageNo페이지 모드 시 페이지 번호
sizeNo페이지 모드 시 페이지 크기
limitNo배치 모드 최종 반환 개수 상한
concurrencyNo배치 모드 페이지 병렬 동시성 (1~10, 기본 5). 높이면 빠르지만 DART 일일 20,000건 한도/분당 쿼터 근접 위험.
Behavior5/5

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

With no annotations, the description fully carries the burden. It discloses parallel fetching, concurrency settings, API quota warnings (daily 20k limit, per-minute quota), and mode behaviors. Also links rcp_no to other tools.

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?

Single dense paragraph covering modes, parameters, and connections. Could be more structured (e.g., bullet points), but every sentence adds value. Concise overall.

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?

Given high schema coverage and no output schema, the description explains core functionality well: modes, parameters, API limits, and tool integration. Lacks output format details but is adequate for selection and invocation.

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%, baseline 3. Description adds context: explains how parameters like preset, all_pages, page, size, limit, concurrency map to modes, and warns about concurrency affecting API quotas. This goes beyond schema descriptions.

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 searches DART disclosures and specifies three distinct modes (basic, preset, all_pages), distinguishing it from siblings like download_document and get_attachments. Uses specific verb 'search' and resource 'disclosures'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the three modes and when to use each, including the preset list and parallel fetching. Mentions concurrency and API quota limits. Does not explicitly list when not to use or compare to all siblings, but provides sufficient guidance.

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/chrisryugj/korean-dart-mcp'

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