Skip to main content
Glama
aesthetic-legalism5470

korean-dart-mcp

get_major_holdings

Retrieve a combined snapshot of large shareholding (5% rule) and insider holdings for any Korean company.

Instructions

지분공시 2종 합성 조회: 대량보유(5%룰) + 임원·주요주주 본인 소유. 내부자·외부 대주주 지분 이력을 한 번에 스냅샷.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNo기간 종료 (미지정 시 오늘)
corpYes회사명/종목코드/corp_code
limitNo최대 반환 행 수 (각 kind 별). 대형 상장사는 누적 수만 건 → 디폴트 200.
startNo기간 시작 (YYYY-MM-DD / YYYYMMDD). 미지정 시 최근 3년.
includeNo조회 대상 (미지정 시 둘 다). majorstock=대량보유 5%룰, elestock=임원·주요주주 본인 보유
Behavior2/5

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

With no annotations, the description carries full behavioral burden. It mentions 'snapshot' but lacks details on data merging, pagination effects, authorization needs, or output structure.

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 concise sentences in Korean with no redundancy, efficiently conveying the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a 5-parameter tool with high schema coverage, but lacks explanation of output structure (no output schema) and how combined results are presented.

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%, so each parameter is already documented. The description adds little extra meaning beyond naming the two disclosure types, which the schema's include parameter already enumerates.

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 is a synthetic query combining two types of equity disclosure (major shareholding and executive holdings), providing a snapshot of insider/outsider history. This distinguishes it from simpler sibling tools like get_shareholders.

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?

The description implies usage for consolidated equity disclosure but provides no explicit guidance on when to use it versus alternatives or when not to use it.

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

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