Skip to main content
Glama
Sign In
toss-securities-mcp

toss-securities-mcp

by hamcheeseburger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_holdings

Retrieve your stock holdings with details on quantity, average price, current price, and profit/loss. Optionally filter by a specific stock symbol.

Instructions

보유 주식을 조회합니다.

사용자가 "보유 종목", "내 주식", "뭐 들고 있어", "삼성전자 몇 주 있어" 등을 물을 때 호출하세요. 종목별 수량·평단가·현재가·평가손익과 전체 합산 요약을 반환합니다. symbol을 지정하면 해당 종목만 조회합니다 (국내: 6자리 코드 예 "005930", 미국: 티커 예 "AAPL").

금액·수량 필드는 정밀도 보존을 위해 문자열입니다. rate 필드는 소수 (0.1077 = +10.77%)입니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description discloses important behavioral traits: return fields (quantity, average price, current price, P/L, summary), data types (strings for precision, decimals for rates). Could mention caching or rate limits, but adequate.

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 well-structured: purpose, usage context, output summary, parameter details, data format notes. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the single parameter and existence of an output schema, the description covers usage, input format, output fields, and data representation thoroughly. No missing critical information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description fully documents the symbol parameter: domestic 6-digit code, US ticker, and optional behavior. This compensates completely for the schema gap.

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?

The description clearly states the specific verb '조회' (query) and the resource '보유 주식' (holdings stocks). It also distinguishes from sibling tools by focusing on holdings versus balance, price, or transactions.

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?

The description provides explicit when-to-use examples ('보유 종목', '내 주식', etc.) and explains the optional symbol filter. It does not explicitly mention alternatives, but context from sibling names makes it clear.

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