tossinvest-mcp

Get order detail

tossinvest_get_order

Read-onlyIdempotent

Retrieve full order details by ID to confirm status and execution results after placing, modifying, or canceling an order.

Instructions

Get the full detail of one order by id, in any state.

Use this to confirm what happened after placing, modifying or cancelling — especially to read the fill result.

Args:

order_id (string): the orderId returned by a create/modify/cancel call or by tossinvest_list_orders.
account_seq (number, optional): resolved automatically for single-account credentials.
response_format ('markdown' | 'json'): default 'markdown'.

Returns { accountSeq, order: { orderId, symbol, side, orderType, timeInForce, status, price, quantity, orderAmount, currency, orderedAt, canceledAt, execution } }. execution = { filledQuantity, averageFilledPrice, filledAmount, commission, tax, filledAt, settlementDate }.

Errors: 404 order-not-found for an unknown id.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`order_id`	Yes	Order identifier (opaque server-issued token).
`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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`order`	Yes
`accountSeq`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive behavior. The description adds value by noting the order can be in 'any state', disclosing the 404 error for unknown ids, and summarizing what fields the response contains. No contradiction with annotations.

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 a clear opening, usage guidance, parameter list, return shape, and error note. Every section serves a purpose and no redundant filler is present.

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 covers purpose, when to use it, parameter origins, response structure, and error behavior. With rich schema annotations and an output schema, nothing critical is missing for an agent to select and invoke the 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 baseline is 3. The description adds useful context beyond the schema by explaining that order_id comes from create/modify/cancel/list_orders calls and that account_seq is auto-resolved for single-account credentials. This helps the agent supply correct inputs.

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 uses a specific verb and resource: 'Get the full detail of one order by id, in any state.' This clearly distinguishes it from list_orders (which lists many) and from create/modify/cancel tools, making its scope unambiguous.

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 explicitly states when to use this tool: 'to confirm what happened after placing, modifying or cancelling — especially to read the fill result.' It also tells where order_id comes from. It does not explicitly name alternatives or state when not to use it, but the context is clear enough.

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

Deploy Server