tossinvest-mcp

List orders

tossinvest_list_orders

Read-onlyIdempotent

List account orders by lifecycle status, choosing OPEN for working orders or CLOSED for finished orders. Filter by symbol and creation date, with pagination for closed orders.

Instructions

List the account's orders, filtered by lifecycle group.

Args:

status ('OPEN' | 'CLOSED'): OPEN returns still-working orders (individual status PENDING, PARTIAL_FILLED, PENDING_CANCEL, PENDING_REPLACE). CLOSED returns finished ones (FILLED, CANCELED, REJECTED, REPLACED, CANCEL_REJECTED, REPLACE_REJECTED, PARTIAL_FILLED).
symbol (string, optional): restrict to one symbol.
from / to (string, optional): YYYY-MM-DD inclusive bounds on order creation time (orderedAt, KST). Omit for all time.
cursor (string, optional): pagination cursor from a previous nextCursor. CLOSED only.
limit (number): 1-100, default 20. CLOSED only.
account_seq (number, optional): resolved automatically for single-account credentials.
response_format ('markdown' | 'json'): default 'markdown'.

Paging differs by status: OPEN returns every working order in one shot and ignores cursor/limit (nextCursor is always null, hasNext always false); CLOSED honours cursor and limit.

Returns { accountSeq, status, count, orders: [...], nextCursor, hasNext }. Each order carries an 'execution' object: { filledQuantity, averageFilledPrice, filledAmount, commission, tax, filledAt, settlementDate }. filledQuantity is 0 when nothing has filled — check it on CANCELED and REJECTED orders too, since those can be partially filled.

Note the two status vocabularies: the 'status' argument is a GROUP label, while 'orders[].status' is the individual order state.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to`	No	Inclusive end date (YYYY-MM-DD, KST) on order creation time.
`from`	No	Inclusive start date (YYYY-MM-DD, KST) on order creation time.
`limit`	No	Page size (max 100). Ignored when status='OPEN'.
`cursor`	No	Pagination cursor from a previous nextCursor. Ignored when status='OPEN'.
`status`	Yes	'OPEN' for working orders, 'CLOSED' for finished orders.
`symbol`	No	Restrict to one symbol. Omit for all symbols.
`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
`count`	Yes
`orders`	Yes
`status`	Yes
`hasNext`	No
`truncated`	No
`accountSeq`	Yes
`nextCursor`	No	Pass as `cursor` for the next page (CLOSED only)
`truncation_message`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A4.6/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 behavior. The description adds substantial context beyond annotations: OPEN returns all working orders in one shot and ignores cursor/limit, CLOSED honors pagination, and filledQuantity is 0 when nothing has filled and must be checked on CANCELED and REJECTED orders.

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 front-loaded with the core purpose, then organized into an Args list and focused behavioral notes. Every sentence earns its place, and the paging and status-vocabulary warnings are concise and high-value.

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 output schema already exists, the description still explains return-shape essentials, pagination semantics, and status vocabularies. Nothing needed for correct invocation appears to be missing.

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

Parameters5/5

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

Even though schema coverage is 100%, the description adds meaning the schema cannot express: the status argument is a group label distinct from orders[].status, cursor/limit are ignored for OPEN, and account_seq has an automatic fallback resolution. This materially improves correct parameter use.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'List the account's orders, filtered by lifecycle group.' It clearly explains the OPEN/CLOSED grouping and goes beyond the title, but it does not explicitly differentiate itself from sibling tools such as tossinvest_get_order or tossinvest_list_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?

Provides clear context for using the status argument, date filters, pagination, and response_format. It does not explicitly say when to prefer this tool over siblings, but the description gives enough operational guidance that an agent can invoke it correctly.

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

Deploy Server