Skip to main content
Glama
scjang01

tossinvest-mcp

by scjang01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Toss Get Orders

toss_get_orders
Read-only

List Toss Securities account orders by status, date range, and symbol, using cursor pagination to retrieve subsequent pages.

Instructions

List orders; preserve nextCursor/hasNext for pagination. OPEN regular orders ignore limit/cursor. When accountSeq is required, call toss_get_accounts first. Select the user's intended account; if multiple accounts are ambiguous, ask the user.

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
limitNo
cursorNo
statusYes
symbolNo
accountSeqYesWhen accountSeq is required, call toss_get_accounts first. Select the user's intended account; if multiple accounts are ambiguous, ask the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. 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=true and destructiveHint=false, so safety is covered. The description adds important behavioral detail beyond annotations: preserve nextCursor/hasNext for pagination, OPEN regular orders ignore limit/cursor, and account selection prerequisites. It stops short of fully describing the response shape or rate limits.

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 four compact sentences with no wasted words. It is front-loaded with the core action ('List orders') and follows with the most important operational constraints.

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 read-only tool with no output schema and only 14% schema description coverage, the description covers critical pagination and account-access behavior but does not fully document most parameter semantics. An agent can call it correctly in common cases but may still need to inspect the schema for other fields.

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 very low at 14%, so the description must compensate. It clarifies accountSeq sourcing and the conditional irrelevance of limit/cursor for OPEN orders, but leaves status values, symbol format, and from/to date semantics unexplained.

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?

The description uses a specific verb and resource ('List orders'), making the core purpose clear. However, it does not differentiate from sibling tools like toss_get_order for a single order or toss_get_conditional_orders, so an agent must infer the boundary.

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?

It gives clear operational guidance: call toss_get_accounts first when accountSeq is required, select the intended account, and ask the user if ambiguous. It does not state when to use this tool instead of the single-order sibling, so alternatives are still implied rather than explicit.

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