Skip to main content
Glama
tossinvest-mcp

tossinvest-mcp

by scjang01

Toss Get Conditional Order

toss_get_conditional_order
Read-only

Retrieves a specific conditional order by account sequence and conditional order ID so you can inspect its details.

Instructions

Get one conditional order by conditionalOrderId.

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>",
      "conditionalOrderId": "<conditionalOrderId>"
    },
    "name": "toss_get_conditional_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountSeqYesCall toss_get_accounts first; ask the user if the intended account is unclear.
conditionalOrderIdYes

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

C2.9/5.0
Behavior2/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 fully covered and the description adds nothing on top. It says nothing about behavior on a missing/invalid ID, account-permission requirements, or whether the order's state (pending/triggered/cancelled) is included.

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?

A single front-loaded sentence with zero filler, and the lookup key is placed where the reader needs it. It is efficient, though the brevity reflects under-specification rather than disciplined editing.

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?

This is a simple two-parameter read, but there is no output schema, so the description bears the burden of describing what a 'conditional order' record contains — and it does not. It also omits failure semantics and the account-scoping prerequisite that the schema only hints at for one parameter.

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 50%: accountSeq carries its own description in the schema (call toss_get_accounts first, ask the user), while conditionalOrderId is undocumented there and is only referenced by name in the description. The description therefore adds marginal meaning beyond the schema rather than real semantics for either parameter.

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?

States a specific verb and resource ('Get one conditional order by conditionalOrderId'), and the word 'one' implicitly distinguishes it from the plural sibling toss_get_conditional_orders. The sibling is not named, so the differentiation is inferable rather than explicit.

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 when-to-use guidance, no named alternative (e.g., use toss_get_conditional_orders to list/filter instead), and no prerequisite describing how an agent obtains a conditionalOrderId in the first place. The agent must infer all routing from the tool name alone.

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