Skip to main content
Glama
kwonsw812

kiwoom-mcp

by kwonsw812

get_account_balance

Read-only

Retrieve account balance details including held stocks, current prices, purchase prices, and total investment amounts from Kiwoom Securities accounts.

Instructions

보유 주식 목록, 현재가, 매입가, 매입금액 등 계좌 잔고를 조회합니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_noNo계좌번호 (미입력시 기본 계좌 사용)

Implementation Reference

  • The underlying API request method for fetching account balance.
    async getAccountBalance(accountNo: string) {
      return this.request("/api/dostk/acnt", "ka10085", {
        acc_no: accountNo,
        stex_tp: "0",
      });
    }
  • src/index.ts:512-526 (registration)
    The MCP tool registration for 'get_account_balance'.
    server.tool(
      "get_account_balance",
      "보유 주식 목록, 현재가, 매입가, 매입금액 등 계좌 잔고를 조회합니다",
      { account_no: accountNoSchema },
      { readOnlyHint: true },
      async ({ account_no }) => {
        try {
          const acct = resolveAccountNo(account_no);
          const data = await client.getAccountBalance(acct);
          return textContent(formatBalance(data));
        } catch (error) {
          return errorContent(formatError(error));
        }
      }
    );
Behavior3/5

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

The description adds some behavioral context beyond the readOnlyHint annotation. It specifies what data is returned (stock holdings, current prices, purchase prices, purchase amounts), which helps the agent understand the scope of information retrieved. However, it doesn't mention important behavioral aspects like whether this requires authentication, rate limits, response format, or error conditions. The annotation correctly indicates read-only operation, and the description doesn't contradict this.

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 extremely concise - a single sentence that efficiently communicates the core functionality. It's front-loaded with the key information (what data is retrieved) without unnecessary elaboration. Every word earns its place in this minimal description.

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 tool's moderate complexity (financial data retrieval), the presence of readOnlyHint annotation, and 100% schema coverage, the description is adequate but has gaps. It explains what data is returned but doesn't cover output format, authentication requirements, or error handling. Without an output schema, the description should ideally provide more detail about the return structure. It meets minimum viable standards but could be more complete.

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?

With 100% schema description coverage, the input schema already fully documents the single optional parameter (account_no with default behavior). The description adds no parameter-specific information beyond what's in the schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no parameter info in the description.

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 description clearly states the tool's purpose: retrieving account balance information including stock holdings, current prices, purchase prices, and purchase amounts. It uses specific verbs ('조회합니다' - retrieves/queries) and resources ('계좌 잔고' - account balance). However, it doesn't explicitly differentiate from sibling tools like 'get_portfolio_summary' or 'get_deposit_detail', which might provide overlapping or related financial information.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_portfolio_summary' (which might provide summary vs detailed balance), 'get_deposit_detail' (which might focus on cash deposits), or 'get_trade_history' (which shows transactions rather than current holdings). There are no explicit when/when-not instructions or prerequisites mentioned.

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/kwonsw812/kiwoom-mcp'

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