Skip to main content
Glama

unfreeze_balance_v2

Destructive

Unfreeze TRX under Stake 2.0 to release staked BANDWIDTH or ENERGY resources, specifying the amount in Sun.

Instructions

Unfreeze TRX to release resources (Stake 2.0).

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": {
      "amount": "<amount>"
    },
    "name": "unfreeze_balance_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesAmount to unfreeze in Sun (1 TRX = 1,000,000 Sun)
networkNoNetwork name. Defaults to mainnet.
resourceNoResource type to release. Defaults to BANDWIDTH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / required
      Added value: +[
      +  "amount"
      +]
  2. First observedv1.1.7

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered by structured fields. The description adds only the Stake 2.0 framing; it omits meaningful behavior such as the unstaking waiting period, the fact that funds are not immediately liquid, and that cancel_all_unfreeze_v2 can reverse it.

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 zero filler; nothing is redundant. Its brevity is efficient, though it edges toward under-specification rather than optimal conciseness.

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?

This is a destructive, non-idempotent state-changing operation with no output schema, yet the description never explains the outcome — e.g., that the unfreeze enters a pending queue and requires a later withdraw step. For a mutation of this consequence, the one-line description leaves real gaps that annotations cannot fill.

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%, including the Sun unit conversion and the BANDWIDTH/ENERGY enum with defaults, so the schema carries parameter meaning fully. The description adds nothing beyond that, which matches the baseline of 3 when the schema does the heavy lifting.

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 — 'Unfreeze TRX to release resources' — and the '(Stake 2.0)' qualifier pins the operation to the newer staking model. It does not explicitly distinguish itself from siblings like freeze_balance_v2, cancel_all_unfreeze_v2, or withdraw_expire_unfreeze, so an agent must infer the boundary.

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, and no mention of the closely related alternatives (cancelling an unfreeze, withdrawing after the waiting period). The agent gets no signal about prerequisites such as available staked resources or the locked-period behavior.

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