Skip to main content
Glama
tossinvest-mcp

tossinvest-mcp

by scjang01

Toss Get Commissions

toss_get_commissions
Read-only

Retrieve trading commission rates and fee information for a specific Toss Securities account. Use it to check costs before placing orders or reviewing account expenses.

Instructions

Get trading commission information for 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>"
    },
    "name": "toss_get_commissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
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."
    • addedInput schema / required
      Added value: +[
      +  "accountSeq"
      +]
  3. First observedv0.1.0

TDQS

B3.1/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, and the description adds nothing beyond them. It does not say whether the result is a per-market fee schedule, rate tiers, or a single blended rate, nor anything about live vs. cached data. For a read tool that is acceptable but leaves real behavioral gaps.

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?

A single front-loaded sentence with no filler or redundancy. Nothing could be removed without losing meaning.

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?

With no output schema, the description is the only place a caller learns what 'commission information' means, and it does not say. Annotations and full parameter coverage carry safety and input semantics, so it is callable, but the return shape and the notion of commissions remain undefined.

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 100% and the account parameter even carries an in-schema instruction to resolve the account via toss_get_accounts, so the schema does the heavy lifting. The phrase 'for an account' only loosely echoes the required parameter without adding format or resolution detail, so the baseline of 3 applies.

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 trading commission information') scoped to an account, which is concrete enough to distinguish it from siblings like toss_get_buying_power or toss_get_holdings. It stops short of explicitly contrasting with any sibling, so it is clear but not maximally differentiated.

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?

The description offers no when-to-use or when-not-to-use guidance and names no alternative tool. The only routing hint ('Call toss_get_accounts first') lives in the input schema, not the description, so the description itself gives an agent no usage context.

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