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

toss-invest-mcp

by jihwan0102
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

preview_order

Read-only

Validate a stock order without placing it: checks limits, balance, and sellable quantity, then returns a preview_id for later confirmation and execution.

Instructions

주문 미리보기 (실제 주문 안 나감). 한도·잔고·매도가능수량을 검사하고 preview_id 를 돌려준다.

  • order_type: LIMIT(지정가), MARKET(시장가), LOC(미국주식 장마감 지정가 = 조건 만족 시 종가에 체결)

  • quantity: 주 수량 (소수점은 미국 시장가 매도만). order_amount_usd: 금액 주문 (미국 시장가만, 정규장 중).

  • price: LIMIT/LOC 필수. LOC 매도는 '이 가격 이상이면 종가로 판다', LOC 매수는 '이 가격 이하면 종가로 산다'. 결과 summary 와 warnings 를 사용자에게 그대로 보여주고, 사용자가 실행하라고 하면 place_order(preview_id) 를 호출한다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>",
      "side": "<side>",
      "order_type": "<order_type>"
    },
    "name": "preview_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYes
priceNo
symbolYes
quantityNo
order_typeYes
order_amount_usdNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with them ('실제 주문 안 나감'). It adds real behavioral context beyond the annotations: it performs limit/balance/sellable-quantity checks, returns a preview_id, and produces summary and warnings that must be surfaced to the user. It does not state whether a preview expires or whether the quoted price is locked, which keeps it from a 5.

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?

Purpose and the safety qualifier are front-loaded, then per-parameter notes, then the follow-up workflow. Dense but every bullet carries actionable content; only minor tightness is lost in the mixed prose/bullet format.

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

Completeness4/5

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

With an output schema present, the return shape needn't be spelled out, and the description still tells the agent to relay summary and warnings to the user. For a 6-parameter trading tool with annotations and an output schema, this covers what an agent needs, though preview_id lifetime is unaddressed.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the load, and it does: it decodes all three order_type enum values including the non-obvious LOC semantics for buys vs. sells, explains the fractional-quantity restriction to US market sells, and states when price is required. Symbol and side are left unexplained, but those are self-evident.

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?

States a specific verb and resource ('주문 미리보기') plus the crucial scope qualifier '(실제 주문 안 나감)' and the concrete side effects it validates (한도·잔고·매도가능수량). This clearly separates it from the sibling place_order, which actually submits the order.

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

Usage Guidelines5/5

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

Gives explicit sequencing: preview first, show summary/warnings to the user, and only call place_order(preview_id) once the user says to execute. The alternative sibling and the condition that selects it are both named, leaving nothing to inference.

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