Skip to main content
Glama

withdraw_expire_unfreeze

Destructive

Withdraw expired unfrozen TRX from Stake 2.0 after the unfreezing period ends, returning it to your available balance.

Instructions

Withdraw expired unfrozen balance (Stake 2.0). Call this after the unfreezing period to return TRX to 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_expire_unfreeze"
  }
}

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

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the risk profile is covered. The description adds real value by describing the state transition (frozen/unfreezing TRX becomes available balance) and the timing gate, but stays silent on what happens if called early (error vs. no-op) and on signing/fee requirements for an on-chain broadcast.

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 sentences, no filler. The action and its Stake 2.0 scoping come first, followed by the timing condition and the resulting effect, which is the right order for an agent deciding whether to call it.

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-parameter, no-output-schema tool with rich annotations, the description covers purpose, precondition and outcome, which is enough to invoke it correctly. The only meaningful gap is failure behavior when the unfreezing period has not yet expired.

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?

There is a single optional 'network' parameter with a schema description stating the mainnet default, giving 100% schema coverage. The description adds no further meaning about the parameter, so the baseline of 3 applies with the schema doing the work.

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?

Names a specific verb ('withdraw') and resource ('expired unfrozen balance') and pins the protocol context as Stake 2.0, so the agent knows exactly which lifecycle stage this acts on. It does not explicitly distinguish itself from siblings like withdraw_balance or get_can_withdraw_unfreeze_amount, so it stops short of a 5.

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 phrase 'Call this after the unfreezing period' gives one clear precondition for use. There is no guidance on what to do instead when the period has not elapsed (e.g., check with get_can_withdraw_unfreeze_amount first) and no exclusion against withdraw_balance, leaving the alternative selection implicit.

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