Skip to main content
Glama

withdraw_balance

Withdraw accumulated TRON voting rewards to the configured wallet's available balance. Specify an optional network, defaulting to mainnet.

Instructions

Withdraw accumulated voting rewards to the configured wallet's available balance.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "withdraw_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.1.7

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the mutating, non-repeatable nature is known. The description usefully adds where the funds come from (voting rewards) and where they land (available balance), but says nothing about failure when there is nothing to withdraw, gas/resource requirements, or irreversibility beyond the annotation.

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?

One front-loaded sentence with zero filler; the effect and the destination are stated in the order an agent needs them.

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 one-optional-parameter mutation with no output schema, the description covers purpose and effect adequately. A note on the no-rewards case or the wallet-configuration requirement would close the remaining gap.

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% for the single optional network parameter, so the schema already carries the default-to-mainnet semantics. The description does not mention network at all, which is acceptable at full coverage but adds no extra meaning.

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 (withdraw) plus the precise resource (accumulated voting rewards) and the destination (the configured wallet's available balance), so an agent can distinguish it from generic balance tools or the unfreeze-withdraw siblings. It stops short of naming those siblings explicitly, so it is clear rather than differentiating.

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 or when-not-to-use guidance, no prerequisite such as having accrued rewards or having a configured wallet, and no pointer to alternatives like withdraw_expire_unfreeze or get_can_withdraw_unfreeze_amount. Only the phrase 'accumulated voting rewards' hints at a precondition.

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