Skip to main content
Glama

cancel_all_unfreeze_v2

Destructive

Cancel TRON unstaking requests to re-stake funds still in the 14-day waiting period and automatically withdraw funds that have passed it to the owner's account.

Instructions

Cancel unstakings, all unstaked funds still in the waiting period will be re-staked, all unstaked funds that exceeded the 14-day waiting period will be automatically withdrawn to the owner’s account.

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": "cancel_all_unfreeze_v2"
  }
}

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
Behavior4/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 safety profile is covered. The description adds genuinely new behavior: funds still inside the waiting period are re-staked, while funds past the 14-day window are automatically withdrawn to the owner's account — a state-dependent, partly irreversible outcome an agent could not infer from the annotations.

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?

One front-loaded sentence with no filler, leading with the action. It is a comma splice that briefly reads as a list of parallel objects, which slightly slows parsing, but no words are wasted.

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?

The effects on funds are well described and no output schema exists to explain. However, for a destructive, non-idempotent, open-world transaction tool the description omits whether it requires owner authorization or a signed broadcast, what happens if there are no pending unstakings, and whether the operation is all-or-nothing.

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 the only parameter (network) defaults to mainnet, so the schema already carries the meaning. The description adds nothing about network selection, which is the expected baseline when the schema does 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?

"Cancel unstakings" is a specific verb+resource pair that identifies the operation unambiguously, and the follow-on clause clarifies the resource's domain (unstaked funds in a 14-day waiting period). It stops short of naming or contrasting with siblings such as unfreeze_balance_v2 or withdraw_expire_unfreeze, so differentiation is left to inference.

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 explains consequences but never states when to invoke it. There is no guidance on when to cancel all unstakings versus using unfreeze_balance_v2, withdraw_expire_unfreeze, or get_available_unfreeze_count first, and no preconditions (ownership, pending proposals, existing unstake entries) are mentioned.

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