Skip to main content
Glama
nangchang

KIS MCP Server

by nangchang

kis_place_domestic_order

Submit cash buy or sell orders for Korean domestic stocks. Choose demo for simulation or real for actual trading.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
envNo'demo'(모의, 기본값) 또는 'real'(실전, 실제 자금 사용 주의!)demo
sideYes'buy'(매수) 또는 'sell'(매도)
priceYes주문단가 (예: '75000', 시장가이면 '0')
exchangeNo거래소: 'KRX'(기본값), 'NXT'KRX
quantityYes주문수량 (예: '10')
account_noNo계좌번호 앞 8자리
order_typeNo주문구분: '00'(지정가, 기본값), '01'(시장가)00
stock_codeYes종목코드 6자리 (예: '005930')
account_prodNo계좌상품코드 2자리
Behavior2/5

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

Without annotations, the description bears the burden of behavioral disclosure. It warns that env='real' uses actual funds, which is important. However, it does not explain order settlement, cancellation rules, or response behavior, leaving significant gaps for a trading tool.

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 very concise with one clear sentence and a specific warning. It is front-loaded with the core action. However, it omits necessary details like response expectations, making it somewhat under-specified.

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 the tool's complexity (9 parameters, no output schema), the description is incomplete. It does not explain the return value, error scenarios, or order lifecycle. A trading tool should provide more context for safe invocation.

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%, so the baseline is 3. The description adds minimal value beyond the schema, only restating the env warning already present in the schema's parameter description. No additional parameter meaning is provided.

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 submits domestic stock cash buy/sell orders, which is a specific verb+resource. However, it does not explicitly distinguish from sibling tools like 'kis_place_overseas_order' or 'kis_revise_or_cancel_domestic_order', though the name and context imply domestic scope.

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, such as when to place an order versus search stocks or check balances. The description only mentions the env parameter's real vs demo mode, but does not help the agent decide between siblings.

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