Skip to main content
Glama
Sign In
tossinvest-mcp

tossinvest-mcp

by scjang01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Toss Get Buying Power

toss_get_buying_power
Read-only

Get available buying power for a specified account and currency—KRW for Korean stocks or USD for US stocks—to check order capacity.

Instructions

Get available buying power for an account. currency is required: KRW for Korean stocks, USD for US stocks.

Input Schema

NameRequiredDescriptionDefault
currencyYesCurrency code: KRW (Korean stocks) or USD (US stocks)
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. 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: -[
-  "currency"
-]New value: +[
+  "accountSeq",
+  "currency"
+]
  2. Changed3 schema fields changedv0.2.0
    • addedInput schema / properties / currency
      Added value: +{
+  "description": "Currency code: KRW (Korean stocks) or USD (US stocks)",
+  "enum": [
+    "KRW",
+    "USD"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / symbol
      Removed value: -{
-  "pattern": "^[A-Za-z0-9.-]+$",
-  "type": "string"
-}
    • addedInput schema / required
      Added value: +[
+  "currency"
+]
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds little behavioral context beyond the currency requirement and does not explain whether buying power is real-time, includes fees, or reflects settled cash versus margin.

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?

Two short sentences with no wasted words. The core purpose is front-loaded, and the currency constraint follows immediately.

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

Completeness4/5

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

For a simple two-parameter read tool with full schema coverage and safety annotations, the description is largely complete. It could mention the accountSeq prerequisite from the schema or what buying power represents, but no critical information is missing for correct invocation.

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 100%, and both parameters are fully documented in the schema. The description reiterates the currency enum meaning but adds no new detail beyond the schema, so the baseline of 3 is appropriate.

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 available buying power for an account.' It is clear what the tool does, but it does not explicitly differentiate itself from related sibling tools such as toss_get_holdings or toss_get_sellable_quantity.

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 clarifies that currency is required and maps KRW to Korean stocks and USD to US stocks. However, it does not state when to use this tool versus alternatives, nor does it mention that accountSeq may require calling toss_get_accounts first—that guidance appears only in the schema.

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