Skip to main content
Glama
Kuco-dev

tossinvest-api-mcp

by Kuco-dev

modifyConditionalOrder

Destructive

Modify a conditional order by replacing its full configuration, including trigger price, order type, and expire date. After modification, a new order ID is issued.

Instructions

조건주문 수정

조건주문을 수정합니다. 조건주문 전체를 재설정하므로 본문에 type·expireDate·first(필요 시 second) 를 모두 전달합니다. 수량(quantity)은 각 감시 조건(first/second) 안에 입력합니다. (등록과 달리 expireDate 가 필수입니다.) 종목은 conditionalOrderId 로 식별되므로 본문에 symbol 은 필요 없습니다. 본문의 type 은 변경 결과 타입이며, 타입 전환(예: SINGLE→OCO)이 허용됩니다. 응답의 type 으로 확인하세요.

conditionalOrderId 로 수정 대상을 식별합니다.

주의: 수정은 기존 조건주문을 취소하고 새 조건주문을 생성하는 방식으로 동작합니다. 따라서 수정 후에는 새로운 conditionalOrderId 가 발급되고 기존 ID 는 무효화됩니다. 이후 조회·수정·취소에는 반드시 응답으로 반환된 conditionalOrderId 를 사용하세요.

Rate Limits Group: CONDITIONAL_ORDER

[POST /api/v1/conditional-orders/{conditionalOrderId}/modify]

tags: Conditional Order

⚠️ 실제 자산에 영향을 주는 조건주문 API 입니다. 기본값은 dryRun=true 이며 실행하려면 TOSSINVEST_ENABLE_CONDITIONAL_ORDERS=true 와 confirmation 이 필요합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes조건주문 수정 요청. 등록과 동일하게 "이 가격에 닿으면 매매" 만 입력하며, 조건주문 전체를 재설정하므로 유지할 조건도 함께 전달해야 합니다. 종목은 `conditionalOrderId` 로 식별되므로 수정 요청에는 `symbol` 이 필요 없습니다.
pathYesURL 경로 파라미터
dryRunNo기본값 true. true 이면 토스증권 서버로 어떤 네트워크 요청도 보내지 않고 실행 계획만 반환합니다. 실제 주문을 내려면 false 로 명시해야 합니다.
accountNo요청에 사용할 계좌의 accountSeq. getAccounts 응답의 accountSeq 값을 사용합니다. 미지정 시 TOSSINVEST_DEFAULT_ACCOUNT 환경변수를 사용하며, 둘 다 없으면 호출하지 않고 오류를 반환합니다.
confirmationNo실주문 확인 문자열. TOSSINVEST_MUTATION_CONFIRMATION 환경변수 값과 정확히 일치해야 실제 주문이 실행됩니다.
Behavior5/5

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

Beyond annotations (destructiveHint=true, readOnlyHint=false), the description reveals critical behavioral details: the modification cancels and recreates the order, resulting in a new conditionalOrderId and invalidation of the old one. It also warns about real asset impact, dryRun default, required confirmation and environment variable, and specifies rate limits group.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately concise but includes some repetition (e.g., explaining the reset behavior in multiple places). While every sentence adds value, the structure could be tightened. The caution and rate limits sections are well-placed, but overall length is acceptable given the complexity.

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, no output schema, and annotations that do not fully explain side effects, the description is comprehensive. It covers the cancellation-and-recreation behavior, new ID issuance, required fields, dryRun mode, confirmation, environment variable, rate limits, and real asset impact. An agent can safely invoke this tool with the provided information.

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 descriptions for all parameters. The description adds value by explaining that type is the result type and transitions are allowed, that expireDate is required here unlike creation, and that symbol is not needed. However, there is a potential contradiction: the description states quantity is inside first/second conditions, but schema shows quantity as a top-level field. This could cause confusion, slightly reducing the score.

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 identifies the tool as modifying a conditional order ('조건주문 수정') and distinguishes it from creation (expireDate required) and cancellation (new ID issued). It specifies that the entire order is reset, leaving no ambiguity about the operation's scope.

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 explains when to use the tool (to modify a conditional order) and provides explicit guidance: send all fields (type, expireDate, first, second if needed), and notes that symbol is unnecessary. It contrasts with creation by stating expireDate is required here. However, it does not explicitly state when to use alternatives like cancelConditionalOrder or createConditionalOrder instead.

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/Kuco-dev/tossinvest-api-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server