Skip to main content
Glama
Sign In
Korean DART MCP

Korean DART MCP

by chrisryugj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_shareholders

Combine four shareholder sections into one governance snapshot: largest shareholder, changes, minority shareholders, and total stocks. Specify sections for focused queries.

Instructions

지배구조 스냅샷: 최대주주·변동·소액주주·주식총수 4개 섹션을 한 번에 합성 조회. (특정 섹션만 필요하면 get_periodic_report 로 단일 조회 가능.)

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": "<corp>",
      "year": "<year>"
    },
    "name": "get_shareholders"
  }
}

Input Schema

NameRequiredDescriptionDefault
corpYes회사명/종목코드/corp_code
yearYes
reportNoannual
sectionsNo조회할 섹션 (미지정 시 4개 모두)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.3

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so description bears full burden. It implies read-only behavior by calling it a 'snapshot' and describes the composite nature, but lacks details on side effects, auth requirements, or rate limits.

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: first states purpose, second provides usage guidance. No redundant information, front-loaded with core functionality.

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?

Despite missing output schema, description gives high-level overview of composite output. However, it lacks details about return format and does not fully address all four parameters.

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 50% with some parameter descriptions; the description adds context by naming the four sections, which maps to the sections enum. However, it does not compensate fully for undocumented parameters like year and report.

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?

Description clearly states it provides a governance snapshot with four specific sections (largest shareholder, changes, minority shareholders, total stocks). It distinguishes itself from sibling tool get_periodic_report by noting that tool can be used for individual sections.

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?

Explicitly mentions when to use get_periodic_report instead if only specific sections are needed. Provides clear context for tool selection, though does not cover all usage scenarios.

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