Skip to main content
Glama
Sign In
Korean DART MCP

Korean DART MCP

by chrisryugj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

download_document

Retrieve original disclosure documents from Korean DART in markdown, XML, or plain text format. Converts DART XML to markdown while preserving headings and tables.

Instructions

공시서류 원문을 마크다운/원본XML/plain text 로 반환합니다. 기본값 markdown — DART 전용 XML 을 자체 파서로 heading·테이블 보존해 변환. 대형 사업보고서는 수백 KB 이상이라 기본 10만 자에서 절단. 사업보고서·반기보고서·주요사항보고 등 모든 공시 원문에 사용.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rcept_no": "<rcept_no>"
    },
    "name": "download_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
rcept_noYes접수번호 14자리 (search_disclosures 의 rcept_no)
formatNo출력 포맷. markdown=DART XML → 마크다운, raw=원본 XML, text=태그 제거markdown
truncate_atNo텍스트 최대 길이 (초과분은 잘림)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.3

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses key behaviors: custom parser for markdown, default truncation at 100,000 characters, and handling of large documents. Missing details like error handling or authentication, but overall transparent for a download tool.

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?

Two sentences with dense, relevant information. No fluff, front-loaded purpose, every sentence adds value. Ideal conciseness.

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?

Covers return formats, custom processing, truncation, and scope. Missing details on error responses or behavior for missing documents, but adequate given the tool's simplicity and full schema coverage.

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%, so baseline is 3. The description adds value by explaining the custom parser for markdown and the truncation behavior, providing context beyond the schema's parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns disclosure documents in markdown, raw XML, or plain text, and mentions the custom parser and default format. However, it doesn't explicitly differentiate from sibling tools like get_periodic_report, which may also return document content.

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?

It says the tool is used for 'all disclosure originals' and lists examples, implying broad usage. However, it lacks explicit when-not-to-use guidance or references to alternatives among siblings, leaving the agent to infer usage context.

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

Deploy Server

Other Tools