Skip to main content
Glama
tossinvest-mcp

tossinvest-mcp

by scjang01

Toss Get Orders

toss_get_orders
Read-only

List regular orders for a Toss Securities account by OPEN or CLOSED status with optional date, symbol, and pagination filters; use nextCursor when hasNext is true.

Instructions

List regular orders. If hasNext, pass nextCursor as cursor. OPEN ignores limit and 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_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
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. Changed3 schema fields 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."
    • removedInput schema / properties / from / pattern
      Removed value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
    • removedInput schema / properties / to / pattern
      Removed value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
  2. Changed8 schema fields changedv0.3.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / accountSeq / description
      Previous value: -"Toss accountSeq. If omitted, TOSSINVEST_ACCOUNT is used."New value: +"When accountSeq is required, call toss_get_accounts first. Select the user's intended account; if multiple accounts are ambiguous, ask the user."
    • addedInput schema / properties / cursor / minLength
      Added value: +1
    • addedInput schema / properties / from / format
      Added value: +"date"
    • changedInput schema / properties / from / pattern
      Previous value: -"^\\d{4}-\\d{2}-\\d{2}$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
    • addedInput schema / properties / to / format
      Added value: +"date"
    • changedInput schema / properties / to / pattern
      Previous value: -"^\\d{4}-\\d{2}-\\d{2}$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
    • changedInput schema / required
      Previous value: -[
      -  "status"
      -]New value: +[
      +  "accountSeq",
      +  "status"
      +]
  3. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real behavior beyond that: it names the pagination contract (hasNext/nextCursor) and a non-obvious status-dependent rule that OPEN ignores limit and cursor, which the agent could not derive from annotations or schema.

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?

Three short sentences, front-loaded with the purpose, then paging rules. Every sentence earns its place, though the extreme terseness leaves 'regular orders' and the OPEN rule ambiguous.

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

Completeness3/5

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

For a 7-parameter, 2-required listing tool with no output schema, the description covers paging but omits date-range semantics, filtering behavior, and default limit. The absence of an output schema means hasNext/nextCursor are the only return fields disclosed, and others go unmentioned.

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 coverage is only 14%, so the description does most of the work for cursor and it flags the OPEN exception for cursor/limit. But from, to, symbol, status and limit semantics (defaults, ordering, date inclusivity) are left entirely to the bare schema.

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

Purpose3/5

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

"List regular orders" gives a verb and a resource, and the word "regular" implicitly separates it from the conditional-order siblings, but it never states what makes an order 'regular' or how it differs from toss_get_order (single order). An agent must infer the scope.

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 description gives operational sequencing (if hasNext, pass nextCursor as cursor) and the OPEN caveat, which is genuinely useful for paging. However, it offers no guidance on when to choose this over toss_get_order or toss_get_conditional_orders, and no prerequisites beyond what the schema already carries.

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