Skip to main content
Glama
nangchang

KIS MCP Server

by nangchang

kis_place_overseas_order

Place overseas stock buy or sell orders for exchanges like NASDAQ, NYSE, and Hong Kong. Supports demo mode for testing and real mode with actual funds.

Instructions

해외주식 매수/매도 주문을 제출합니다. env='real'이면 실제 자금이 사용됩니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
envNo'demo'(모의, 기본값) 또는 'real'(실전, 실제 자금 사용 주의!)demo
sideYes'buy'(매수) 또는 'sell'(매도)
priceYes주문단가 (시장가이면 '0')
symbolYes종목코드 (예: 'AAPL')
exchangeYes거래소코드: NASD(나스닥), NYSE(뉴욕), AMEX, SEHK(홍콩), SHAA, SZAA, TKSE, HASE, VNSE
quantityYes주문수량
account_noNo계좌번호 앞 8자리
order_typeNo주문구분: '00'(지정가, 기본값)00
account_prodNo계좌상품코드
Behavior3/5

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

With no annotations, the description carries full burden. It mentions the behavioral trait that env='real' uses real funds, which is critical. However, it does not cover other behavioral aspects such as irreversibility, authorization needs, or rate limits. Adequate but not comprehensive.

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 with two sentences, no fluff, and effectively front-loads the purpose. Every word earns its place.

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

Completeness2/5

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

Given this is a financial order placement tool with 9 parameters, 5 required, and no output schema, the description is too brief. It lacks information about order confirmation, error handling, or processing behavior, leaving the agent underinformed.

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?

Schema description coverage is 100%, and the description adds no additional meaning beyond the schema. It does not explain or highlight any parameters, so it meets the baseline of 3 without adding value.

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 tool submits overseas stock buy/sell orders, specifying '해외주식' to distinguish it from domestic order tools. It also includes the env warning, which adds context.

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 implies usage for overseas orders but does not explicitly state when to use this tool versus alternatives like kis_place_domestic_order. No exclusions or when-not-to-use guidance is provided.

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/nangchang/stock-kis-mcp'

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