Skip to main content
Glama
kwonsw812

kiwoom-mcp

by kwonsw812

get_portfolio_summary

Read-only

Analyze your portfolio's total valuation, profit/loss, and return rate to monitor overall investment performance.

Instructions

총평가금액, 총손익, 수익률 등 포트폴리오 전체 현황을 분석합니다

Input Schema

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

Implementation Reference

  • Handler implementation for 'get_portfolio_summary' tool, which fetches account evaluation data using the client and formats it.
    server.tool(
      "get_portfolio_summary",
      "총평가금액, 총손익, 수익률 등 포트폴리오 전체 현황을 분석합니다",
      { account_no: accountNoSchema },
      { readOnlyHint: true },
      async ({ account_no }) => {
        try {
          const acct = resolveAccountNo(account_no);
          const data = await client.getAccountEvaluation(acct);
          return textContent(formatPortfolioSummary(data));
        } catch (error) {
          return errorContent(formatError(error));
        }
      }
Behavior3/5

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

The annotations already declare readOnlyHint=true, indicating this is a safe read operation. The description adds useful context about what gets analyzed (portfolio valuation, profit/loss, returns), which helps the agent understand the scope of data returned. However, it doesn't disclose additional behavioral traits like rate limits, authentication needs beyond the account_no parameter, or whether it requires specific permissions. No contradiction with annotations exists.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple read operation and front-loaded with key information (what gets analyzed). Every part of the sentence contributes value by specifying the analysis scope.

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 low complexity (1 optional parameter, read-only operation), no output schema, and rich annotations (readOnlyHint), the description is adequate but has gaps. It explains what data is analyzed but doesn't cover return format details, error conditions, or how the analysis is presented (e.g., aggregated values vs. breakdowns). For a portfolio summary tool, more context on output structure would be helpful despite the annotations.

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 single parameter 'account_no' clearly documented in the schema ('계좌번호 (미입력시 기본 계좌 사용)' - account number, uses default if not input). The description doesn't add any parameter-specific information beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without compensating value.

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 what the tool does ('분석합니다' - analyzes) and specifies the resources it analyzes ('총평가금액, 총손익, 수익률 등 포트폴리오 전체 현황' - total valuation, total profit/loss, rate of return, and overall portfolio status). It distinguishes from siblings like get_account_balance (specific balance) or get_trade_history (transaction history) by focusing on comprehensive portfolio analysis. However, it doesn't explicitly name the sibling alternatives for comparison.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by specifying it analyzes '포트폴리오 전체 현황' (overall portfolio status), suggesting it's for summary views rather than detailed transactions or specific stock data. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like get_account_balance (for balance only) or get_trade_history (for transaction details), nor does it mention any 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/kwonsw812/kiwoom-mcp'

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