tossinvest-mcp

Get conditional order detail

tossinvest_get_conditional_order

Read-onlyIdempotent

Retrieve full details of a conditional order by ID, including status, type, prices, and leg information. Use the ID from a create/modify response or the list endpoint to inspect active or finished orders.

Instructions

Get the full detail of one conditional order by id, active or finished.

Args:

conditional_order_id (string): id from a create/modify response or from tossinvest_list_conditional_orders.
account_seq (number, optional): resolved automatically for single-account credentials.
response_format ('markdown' | 'json'): default 'markdown'.

Returns { accountSeq, conditionalOrder: { conditionalOrderId, type, status, symbol, market, quantity, orderType, expireDate, createdAt, first, second } }. Each leg has { type, status, triggerPrice, targetProfitRate, orderPrice, triggeredOrderId }. Leg status values: WATCHING, HOLDING, PAUSED, ORDERING, ORDERED, COMPLETED, EXPIRED, CANCELED.

Errors: 404 conditional-order-not-found — note that modifying a conditional order issues a NEW id and voids the old one, so always use the most recently returned id.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`account_seq`	No	accountSeq of the account to act on (the `X-Tossinvest-Account` header). Optional: falls back to TOSSINVEST_ACCOUNT_SEQ, then to the sole account on the credentials. Get valid values from tossinvest_list_accounts.
`response_format`	No	Output format: 'markdown' for a compact human-readable summary, 'json' for the complete raw payload.	markdown
`conditional_order_id`	Yes	Conditional order identifier.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`accountSeq`	Yes
`conditionalOrder`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive, and the description adds substantial behavioral context beyond that: it can retrieve active or finished orders, 404 behavior, and the critical caveat that modifying an order issues a new ID and voids the old one. This is exactly the kind of behavioral disclosure that helps an agent avoid stale-ID mistakes.

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 well-structured with clear sections (overview, args, returns, errors). Every sentence carries useful information, and the most critical operational warning about ID invalidation is prominently included. No filler or redundancy.

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?

The description is fully complete for this tool: it covers parameter sources, optional fallback behavior, response shapes for legs, status enums, error scenarios, and the important ID lifetime caveat. Combined with the annotations and output schema, an agent has everything needed to call this tool 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%, so the baseline is 3, but the description adds meaning beyond the schema by specifying that conditional_order_id should come from a create/modify response or list call, and that account_seq is automatically resolved for single-account credentials. This enriches the schema's minimal 'Conditional order identifier.' description.

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 states a specific verb ('Get'), a specific resource ('full detail of one conditional order'), and a clear scope ('by id, active or finished'). It clearly differentiates from sibling tools like tossinvest_list_conditional_orders (list vs. detail) and tossinvest_get_order (regular orders vs. conditional orders).

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

Usage Guidelines4/5

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

The description gives clear context for use: it explains where valid IDs come from (create/modify response or tossinvest_list_conditional_orders) and warns that modifying a conditional order invalidates the old ID, telling the agent to always use the most recent ID. It does not explicitly state when-not-to-use or name alternatives, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server