Skip to main content
Glama
Sign In
dart-search-mcp

dart-search-mcp

by memorise8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_major_shareholders_report

Retrieve major shareholder status reports from DART for a specific company, including holdings, changes, and reasons.

Instructions

DART에서 대량보유 상황보고 정보를 조회합니다.

특정 기업의 주식 등을 대량보유(5% 이상)한 자의 보유 현황 및 변동 내역을 반환합니다.

Parameters:
    corp_code: DART 고유번호 (8자리, 예: "00126380")

Returns:
    대량보유 상황보고 목록
    - 접수번호, 접수일자
    - 보고서구분 (보유/변동)
    - 보고자명
    - 보유주식수 및 증감
    - 보유비율 및 증감
    - 변동사유

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": {
      "corp_code": "<corp_code>"
    },
    "name": "get_major_shareholders_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
corp_codeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 burden. It describes the output fields (접수번호, 접수일자, 등) and implies a read-only query. However, it does not disclose potential behaviors like rate limits, data coverage, or whether results are historical only. The description is adequate but lacks some behavioral context.

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?

The description is concise, front-loading the main purpose, then detailing parameter and returns. Each sentence serves a purpose, with no fluff. Slightly verbose due to Korean formatting, but overall efficient.

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 the simple single-parameter tool and the presence of an output schema, the description is fairly complete. It explains the parameter format and lists return fields. Missing details like error handling or data range, but these are not critical for this straightforward query tool.

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?

The input schema has one parameter (corp_code) with 0% description coverage. The description adds meaning by stating it is an 8-character DART unique number with an example ('00126380'), which compensates for the schema's lack of detail. This provides valuable guidance beyond the schema.

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 the tool retrieves major shareholders report information from DART, specifying it returns holder status and changes for those holding 5% or more. The verb '조회' (retrieve) and resource '대량보유 상황보고 정보' are specific, and the details distinguish it from sibling tools like get_major_event_report.

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?

The description indicates the required parameter (corp_code) with format example, implying use for major shareholder reports. However, it does not explicitly compare with sibling tools or state when not to use it. Context is clear but lacks exclusion criteria.

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