Skip to main content
Glama
tossinvest-mcp

tossinvest-mcp

by scjang01

Toss Get Conditional Orders

toss_get_conditional_orders
Read-only

Retrieve conditional orders for a Toss Securities account filtered by OPEN or CLOSED status. Use the returned nextCursor with cursor to page through results when hasNext is true.

Instructions

List conditional orders. If hasNext, pass nextCursor as 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": {
      "accountSeq": "<accountSeq>",
      "status": "<status>"
    },
    "name": "toss_get_conditional_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
statusYes
symbolNo
accountSeqYesCall toss_get_accounts first; ask the user if the intended account is unclear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.2
    • changedInput schema / properties / accountSeq / description
      Previous value: -"When accountSeq is required, call toss_get_accounts first. Select the user's intended account; if multiple accounts are ambiguous, ask the user."New value: +"Call toss_get_accounts first; ask the user if the intended account is unclear."
  2. Addedv0.3.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description does add real behavioral value by explaining the hasNext/nextCursor pagination contract, which is otherwise invisible since there is no output schema. It stops short of explaining what a conditional order is, what statuses mean, or what fields come back.

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

Conciseness4/5

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

Two short sentences with the primary purpose front-loaded and the pagination rule second; nothing is padded. The very brevity is what leaves gaps, but the sentences themselves each earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters, 20% schema coverage, no output schema, and a required status filter, this description is underpowered for the tool's complexity. An agent gets no sense of what conditional orders contain, how status constrains the listing, or what the accountSeq requirement implies at call time.

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

Parameters3/5

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

Schema description coverage is only 20% (only accountSeq is documented), so the description carries extra burden. It does add genuine meaning by mapping the response field nextCursor onto the request parameter cursor, which the schema alone would not reveal. However, status, limit, and symbol receive no explanation beyond their schema types and enum/pattern constraints, leaving the coverage gap only partly closed.

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?

"List conditional orders" gives a specific verb and resource, so the agent immediately knows this is a read of a collection. It does not distinguish itself from the singular sibling toss_get_conditional_order (detail vs. list) or from toss_get_orders, so the last discriminating step is left to inference.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus toss_get_conditional_order or toss_get_orders, and no mention that status is required to scope the query. The only procedural hint is the pagination loop, which is about invocation mechanics rather than tool selection.

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