Skip to main content
Glama
tossinvest-mcp

tossinvest-mcp

by scjang01

Toss Get Order

toss_get_order
Read-only

Retrieves a single regular securities order by order ID and account sequence, helping you inspect its status and details for a specific account.

Instructions

Get one regular order by orderId.

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>",
      "orderId": "<orderId>"
    },
    "name": "toss_get_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYes
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. Changed3 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."
    • changedInput schema / required
      Previous value: -[
      -  "orderId"
      -]New value: +[
      +  "accountSeq",
      +  "orderId"
      +]
  3. First observedv0.1.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, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the meaningful qualifier "regular", telling the agent conditional orders cannot be retrieved here, but says nothing about not-found/error behavior or what a returned order looks like.

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?

A single front-loaded sentence with zero filler, which is efficient. However, for a financial lookup tool it is arguably undersized — the terseness leaves no room for prerequisites or scope caveats.

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?

The tool is simple (two required params, rich annotations, no output schema), so the description needn't explain return values. Still, it omits the accountSeq prerequisite and the orderId format, both of which an agent needs in order to call it correctly on the first attempt.

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 50%: accountSeq is well documented in the schema, but orderId has no format or provenance description there. The description mentions orderId as the lookup key but adds no syntax, source, or example, so the gap is not fully compensated.

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 states a specific verb and resource ("Get one regular order") and scopes it to a single lookup keyed by orderId. The words "one" and "regular" implicitly separate it from the list-style toss_get_orders and the conditional-order tools, though no sibling is named explicitly.

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 explicit when-to-use or when-not-to-use guidance, and no stated prerequisites (the accountSeq dependency lives only in the schema). An agent must infer from "one ... by orderId" that listing belongs elsewhere and that conditional orders are out of scope.

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