Skip to main content
Glama
Sign In
opendart-fss-mcp

opendart-fss-mcp

by hypn4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

report_largest_shareholder_changes

Read-only

Retrieve largest shareholder changes for any Korean corporation. Specify corporate code, business year, and report code to access official DART disclosure data.

Instructions

최대주주 변동 현황을 조회합니다.

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>",
      "bsns_year": "<bsns_year>",
      "reprt_code": "<reprt_code>"
    },
    "name": "report_largest_shareholder_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
corp_codeYes고유번호 (8자리)
bsns_yearYes사업연도 (YYYY)
reprt_codeYes보고서코드 (11011:사업, 11012:반기, 11013:1분기, 11014:3분기)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, which inform the agent of safe read-only behavior and possible continuation. The description adds the nature of the data (changes) but does not elaborate on further behavioral traits like pagination or data freshness. Given the annotations, a score of 3 is adequate.

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 a single short sentence that is front-loaded and contains no extraneous information. It is appropriately concise for 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?

Given the existence of an output schema, the description does not need to detail return values. However, the brief description could be more helpful by explaining what constitutes a 'change' (e.g., compared to previous reporting period). It is minimally complete but could be improved.

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?

Input schema coverage is 100%, so the schema already describes all three parameters with their meaning and format. The description adds no additional semantic information beyond what the schema provides, resulting in a baseline score of 3.

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 Korean description '최대주주 변동 현황을 조회합니다.' clearly states the tool retrieves changes in the largest shareholder. It uses a specific verb and resource, and implicitly distinguishes from sibling like 'report_largest_shareholders' which would be a snapshot. However, it does not explicitly differentiate from alternatives.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus sibling tools such as 'report_largest_shareholders' or 'report_stock_changes'. There is no description of context, prerequisites, or exclusions.

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