Skip to main content
Glama
Jeric1223

tossinvest-mcp

Prepare stock order

toss_prepare_order
Destructive

Preview a new market or limit order to buy or sell a stock. Validates the request and returns a confirmation token for later submission after user approval.

Instructions

Previews a NEW market or limit order to buy or sell one stock immediately. For trigger-based orders use toss_prepare_conditional_order; to change or withdraw an order that already exists use toss_prepare_order_modify or toss_prepare_order_cancel. Nothing reaches the market from this call: it only validates the request and returns a preview plus a confirmation token. Show that preview to the user, obtain explicit approval, then pass the token to toss_submit_prepared_order. The token is single-use and expires 60 seconds after this call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sideYesBUY to open or increase a position, SELL to reduce or close one.
priceNoLimit price as a positive decimal string. Required for LIMIT, rejected for MARKET.
symbolYesKorean 6-digit code (e.g. '005930') or US ticker (e.g. 'NVDA'). Call toss_resolve_symbol first if you only have a company name.
quantityNoShare count as a positive decimal string. Provide exactly one of `quantity` or `orderAmount`.
orderTypeYesLIMIT executes only at `price` or better and requires `price`. MARKET executes at the prevailing price and must omit `price`.
orderAmountNoCash amount to spend instead of a share count, as a positive decimal string. Valid only for MARKET orders. Provide exactly one of `quantity` or `orderAmount`.
timeInForceNoDAY keeps the order working for the current session; CLS routes it to the closing auction. Defaults to DAY when omitted.
Behavior1/5

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

The description states "Nothing reaches the market from this call" and describes the token as single-use with 60-second expiry, but the annotations declare destructiveHint=true, implying destructive side effects. This directly contradicts the description's explicit claim of no market impact, so the transparency score is 1 due to the annotation contradiction.

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 four sentences, front-loaded with the core action, then presents alternatives, safety behavior, and workflow. Every sentence adds essential information without redundancy or fluff.

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?

The description covers the core behavior (preview, nothing reaches market), token lifecycle, workflow, and sibling distinctions. However, with no output schema, it does not detail the structure of the preview (e.g., estimated price, fees), leaving a minor gap in return-value expectations.

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%, with each parameter (symbol, side, orderType, price, quantity, orderAmount, timeInForce) having a detailed explanation. The tool description itself adds no parameter-specific meaning beyond the schema, so the baseline score of 3 is appropriate.

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 opens with a specific verb and resource: "Previews a NEW market or limit order to buy or sell one stock immediately." It explicitly differentiates from siblings by naming toss_prepare_conditional_order for trigger-based orders and toss_prepare_order_modify/cancel for existing orders, making the tool's purpose unmistakable.

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?

The description provides explicit when-to-use guidance: "For trigger-based orders use toss_prepare_conditional_order; to change or withdraw an order that already exists use toss_prepare_order_modify or toss_prepare_order_cancel." It also clearly outlines the workflow: show preview, obtain approval, pass token to toss_submit_prepared_order.

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/Jeric1223/tossinvest-mcp'

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