kiwoom-private-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KIWOOM_USE_MOCK | No | Set to 'true' to use mock data, 'false' to use real Kiwoom API | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_accountsB | 설정된 키움증권 계좌 목록과 각 계좌별로 지정된 타겟 섹터 및 상세 설명을 조회합니다. Returns: JSON 형식의 계좌 목록 데이터 |
| get_account_balanceA | 특정 계좌의 총 평가 자산 및 상세 보유 종목 리스트(평가금액, 비중, 평단가 등)를 조회합니다. Args: account_no: 조회할 키움증권 계좌 번호 (예: '61724222') use_mock: Mock 데이터를 강제로 사용할지 여부 (기본값: None, .env의 KIWOOM_USE_MOCK 설정을 따름) Returns: JSON 형식의 계좌 잔고 및 보유 종목 데이터 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools, get_account_balance and get_accounts, have clearly distinct purposes: one retrieves detailed holdings and balance for a specific account, while the other lists all accounts with their metadata. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun snake_case pattern (get_account_balance, get_accounts). The naming is predictable and clearly indicates the action and resource.
With only two tools, the server is well below the typical 3-15 tool range for a comprehensive service. While the tools are focused, a trading platform like Kiwoom would typically require many more operations (e.g., placing orders, history), making the tool set feel incomplete.
The tool set only covers reading account info (list and balance). For a securities trading server, obvious operations like order management, stock search, and transaction history are missing. This leaves significant gaps that would hinder agent workflows.