Skip to main content
Glama
minking
by minking

call_dart_api

Calls any official Open DART endpoint and returns the raw JSON response with automatic API key injection.

Instructions

금융감독원 Open DART의 모든 공식 엔드포인트를 호출하여 원본 JSON을 가공 없이 그대로 반환합니다. (DART_API_KEY 자동 주입)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNoDART 요청 파라미터 객체 (예: corp_code, bsns_year: "2023", reprt_code: "11011"[사업보고서], "11012"[반기], "11013"[1분기], "11014"[3분기] 등)
endpointYesDART 공식 JSON 엔드포인트 카탈로그: - 공시검색/개황: list.json(공시검색), company.json(기업개황) - 재무제표: fnlttSinglAcnt.json(단일회사 주요계정), fnlttMultiAcnt.json(다중회사 최대 10개사 주요계정 일괄비교), fnlttSinglAcntAll.json(단일회사 전체 재무제표) - 정기보고서 주요정보: alotMatter.json(배당), hyslrSttus.json(최대주주), hyslrChgSttus.json(최대주주변동), mrhlSttus.json(소액주주), exctvSttus.json(임원), empSttus.json(직원), indvdlByPay.json(5억이상보수), hmvAuditIndvdlBySttus.json(이사감사보수), otrCprInvstmntSttus.json(타법인출자), crpTotlIdex.json(증자감자), tesstkAcqDspsSttus.json(자기주식) - 지분공시: majorstock.json(대량보유 5% 보고), elestock.json(임원/주요주주 소유상황) - 주요사항보고서: ic.json(유상증자), fcr.json(무상증자), cr.json(유무상증자), rd.json(감자), act.json(자기주식취득), dst.json(자기주식처분), cvbd.json(전환사채), bw.json(신주인수권부사채), eb.json(교환사채), mrg.json(합병), div.json(분할), atras.json(자산양수도), obpr.json(주식양수), ospr.json(주식양도) 등 24종

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses automatic DART_API_KEY injection and that the response is the original, unprocessed JSON. However, it omits operational traits such as rate limits, possible DART error payloads, or explicit read-only semantics.

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 one concise, front-loaded sentence plus a short parenthetical about API key injection. Every word earns its place, and there is no redundancy with the schema.

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?

The description plus the detailed endpoint catalog in the schema gives an agent enough to select an endpoint, pass params, and understand the raw JSON return shape and automatic auth. It stops short of a 5 because it omits operational caveats such as rate limits and error behavior, and gives no alternative-tool routing.

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%, with rich parameter documentation in the input schema itself, including the endpoint catalog and reprt_code mappings. The tool description adds no parameter-level detail beyond that, so the baseline score of 3 applies.

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 uses a specific verb and resource: it calls Open DART official endpoints and returns raw JSON without processing. It clearly distinguishes itself from the KRX/document/corp-code siblings by naming the DART API scope and the unprocessed-output contract.

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

Usage Guidelines3/5

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

Usage is implied rather than explicit: the description indicates this tool is for hitting Open DART endpoints and getting raw JSON, but it does not state when to prefer it over siblings like download_dart_document or search_corp_code. There is no when-not-to-use guidance.

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