Skip to main content
Glama
Jeric1223

tossinvest-mcp

Prepare conditional stock order

toss_prepare_conditional_order
Destructive

Preview a conditional order (SINGLE, OCO, OTO) that waits for a trigger price, returning a token for later approval. For take-profit/stop-loss pairs, no trade is placed.

Instructions

Previews a NEW conditional order that stays dormant until its trigger price is reached. SINGLE arms one leg. OCO arms two legs where filling either one cancels the other (typical take-profit plus stop-loss pair). OTO arms a second leg that is placed only after the first leg fills. For an order that should execute right away use toss_prepare_order instead. 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
typeYesSINGLE uses `first` only. OCO and OTO both require `second`.
firstYesPrimary leg, armed as soon as the order is accepted.
secondNoSecond leg. Required for OCO and OTO; must be omitted for SINGLE.
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.
quantityYesShare count for the order, as a positive decimal string.
orderTypeYesLIMIT requires `orderPrice` on every leg. MARKET forbids it. OCO and OTO accept LIMIT only.
expireDateYesLast KST date the condition stays armed, formatted YYYY-MM-DD, e.g. '2026-12-31'.
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: it only validates...' but annotations include destructiveHint: true. This is a direct contradiction: the description implies non-destructive behavior while the annotation flags destructiveness. Therefore, score is 1.

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 information-dense with no fluff. Every sentence contributes: definition, order type semantics, alternative, validation behavior, workflow, and token details. Well-structured and front-loaded.

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 tool's complexity (multiple order types, nested leg objects, no output schema), the description covers essential aspects: it returns a preview and token, explains token single-use and 60-second expiry, and describes the submission flow. Broad enough for an agent to use correctly.

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 coverage is 100% with each parameter already described. The description adds meaningful context beyond the schema by explaining the behavioral differences between SINGLE, OCO, and OTO, and how orderType interacts with legs. This supplements the structured field descriptions.

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's function: previews a NEW conditional order that remains dormant until trigger price is reached. It also differentiates from the sibling toss_prepare_order for immediate execution. Specific enough to distinguish from related tools.

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?

Explicitly names toss_prepare_order as the alternative when execution is needed right away. Also outlines the full workflow: show preview to user, get approval, pass token to toss_submit_prepared_order, and notes token expiry. This gives clear when-to-use and how-to-use guidance.

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