Skip to main content
Glama
tossinvest-mcp

tossinvest-mcp

by scjang01

Toss Get Sellable Quantity

toss_get_sellable_quantity
Read-only

Retrieve the sellable quantity of a specific stock symbol in an account to verify how many shares can be sold before placing an order.

Instructions

Get sellable quantity for one symbol in an account.

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>",
      "symbol": "<symbol>"
    },
    "name": "toss_get_sellable_quantity"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
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: -[
      -  "symbol"
      -]New value: +[
      +  "accountSeq",
      +  "symbol"
      +]
  3. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare read-only, non-destructive, open-world behavior, so the description owes little on safety, but it adds nothing else. The key domain concept — what 'sellable' excludes (pending sell orders, locked shares, unsettled positions) — is left undefined, and no rate-limit or freshness behavior is mentioned.

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 no filler; nothing is redundant. It is terse to the point of under-specification, but that is captured in other dimensions rather than penalized here.

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?

The call is simple and there is no output schema burden, yet the description never explains the returned quantity's semantics or units, which is the main thing an agent needs before trusting the number. For a domain-specific financial lookup, this leaves a real gap.

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

Parameters2/5

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

Schema coverage is only 50%: accountSeq carries a usage hint while symbol only has a regex pattern. The description's phrase 'one symbol in an account' merely restates requiredness and adds no format, market-suffix, or account-resolution detail to compensate for the sparse schema.

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 sellable quantity) scoped to one symbol and one account, which is enough to separate it from siblings like toss_get_holdings or toss_get_buying_power. It does not explicitly name those alternatives, but the resource is distinct enough that an agent can tell what it fetches.

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 at all: nothing says why an agent would pick sellable quantity over buying power or holdings, nor any precondition such as requiring a resolved accountSeq. Usage is only implied by the tool name.

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