Skip to main content
Glama
kwonsw812

kiwoom-mcp

by kwonsw812

get_deposit_detail

Read-only

Retrieve detailed deposit information including available funds, margin requirements, and unsecured amounts for Kiwoom Securities accounts to manage trading capital effectively.

Instructions

예수금, 증거금, 미수확보금 등 예수금 상세를 조회합니다

Input Schema

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

Implementation Reference

  • The get_deposit_detail tool is defined and registered using server.tool. It uses the client.getDeposit method to fetch the data and formats the output using formatDeposit.
    server.tool(
      "get_deposit_detail",
      "예수금, 증거금, 미수확보금 등 예수금 상세를 조회합니다",
      { account_no: accountNoSchema },
      { readOnlyHint: true },
      async ({ account_no }) => {
        try {
          const acct = resolveAccountNo(account_no);
          const data = await client.getDeposit(acct);
          return textContent(formatDeposit(data));
        } catch (error) {
          return errorContent(formatError(error));
        }
      }
    );
Behavior3/5

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

The annotations indicate readOnlyHint=true, which the description aligns with by using '조회합니다' (retrieves/views). The description adds value by specifying the types of deposit details retrieved (예수금, 증거금, 미수확보금), but does not disclose additional behavioral traits like rate limits, authentication needs, or response format, relying on annotations for basic safety.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence in Korean that directly states the tool's function. It is front-loaded with the core purpose and avoids unnecessary words, though it could be slightly more structured for clarity in English contexts.

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 simplicity (one optional parameter, read-only annotation, no output schema), the description is adequate but minimal. It covers the purpose but lacks context on output format, error handling, or integration with sibling tools, leaving gaps for an agent to fully understand usage in a financial system.

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?

The input schema has 100% description coverage, with the parameter 'account_no' fully documented in the schema. The description does not add any parameter-specific information beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high schema coverage.

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 detailed deposit information including deposit money, margin, and unsecured loan collateral. It uses specific financial terms (예수금, 증거금, 미수확보금) that define the scope, though it doesn't explicitly differentiate from sibling tools like 'get_account_balance' or 'get_portfolio_summary' which might overlap in financial data retrieval.

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 alternatives. The description does not mention any prerequisites, exclusions, or comparisons to sibling tools such as 'get_account_balance' or 'get_portfolio_summary', leaving the agent to infer usage context from tool names alone.

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