Skip to main content
Glama
Sign In
tossinvest-mcp

tossinvest-mcp

by clauzewitz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_orders

Read-onlyIdempotent

Fetch stock orders by status—OPEN (unfilled, returned in full) or CLOSED (paginated via cursor)—and filter by symbol, account, or order date range.

Instructions

주문 목록을 조회한다. 앱·WTS 주문도 포함, 주문 1건 = 1행(분할 체결 합산).

OPEN 은 페이지 없이 전량, CLOSED 는 limit 개씩 cursor 로 넘긴다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "status": "<status>"
    },
    "name": "list_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo페이지 크기 (최대 100)
cursorNoCLOSED 다음 페이지: 이전 응답의 nextCursor
statusYesOPEN 미체결·진행 중 (전량), CLOSED 체결·취소·거부 등 종료
symbolNo종목 필터
to_dateNo주문일 끝 YYYY-MM-DD (KST, 포함)
from_dateNo주문일 시작 YYYY-MM-DD (KST, 포함)
account_seqNo계좌 accountSeq (list_accounts 로 확인). 생략하면 TOSSINVEST_ACCOUNT_SEQ 설정값

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds non-obvious behavior beyond that: app/WTS orders are included, split executions are merged into a single row, and paging semantics differ by status. It does not describe the returned fields, but that is a minor gap given the 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?

Two short sentences with no filler. The core purpose and the row-granularity rule come first, and the paging rule follows, so the most important information is front-loaded.

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?

For a 7-parameter read tool with no output schema, the description covers the two things an agent could get wrong: row granularity and status-dependent paging. It does not sketch the shape of the returned order records, which leaves a small gap, but the schema documents every parameter including the account default.

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 would be 3, but the description adds a cross-parameter constraint the schema does not express: limit and cursor only apply when status is CLOSED, while OPEN ignores paging entirely. That is genuine meaning beyond the per-field descriptions.

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 ('주문 목록을 조회한다') and adds scope detail that separates it from a single-order lookup: app/WTS orders are included and one order equals one row with split fills aggregated. It never names the sibling get_order explicitly, so the differentiation is implied rather than stated.

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

Usage Guidelines3/5

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

The second sentence gives real operational guidance on how to page through results depending on status (OPEN returns everything without paging, CLOSED pages by limit/cursor). However, there is no guidance on when to choose this tool over get_order or list_conditional_orders, and no prerequisites or exclusions are stated.

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

Deploy Server

Other Tools