Skip to main content
Glama
hypn4

opendart-fss-mcp

by hypn4

shareholder_major_stock

Read-only

Retrieve major shareholder holdings for a Korean corporation by providing its 8-digit corporate code. Access official data from Korea's DART disclosure system.

Instructions

대량보유 현황을 조회합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
corp_codeYes고유번호 (8자리)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Annotations already indicate readOnlyHint=true and openWorldHint=true, which cover safety and data freshness. The description adds no additional behavioral context (e.g., data source, refresh rate, or permission requirements) beyond what annotations provide.

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 concise sentence that directly states the tool's purpose. No extraneous words, front-loaded, and efficient.

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

Completeness2/5

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

The description is too brief for a domain-specific tool. It does not explain what 'major holdings' includes, nor does it differentiate from numerous sibling tools. The output schema exists but is not described, leaving gaps in understanding the return data.

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% with a clear description for 'corp_code'. The tool description itself does not elaborate on the parameter, but the schema already covers it. Baseline score of 3 is appropriate as no extra semantic value is added.

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

Purpose3/5

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

The description states it inquires about major holdings status, which aligns with the tool name. However, it does not specify what aspect of major holdings (e.g., current holdings, changes, or percentages), making it somewhat vague compared to sibling tools like 'report_largest_shareholder_changes' or 'report_largest_shareholders'.

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 on when to use this tool versus alternatives such as 'shareholder_executive_stock' or 'report_largest_shareholders'. There is no mention of use cases, prerequisites, or exclusions.

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/hypn4/opendart-fss-mcp'

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