Skip to main content
Glama

get_can_withdraw_unfreeze_amount

Read-onlyIdempotent

Retrieves the withdrawable unstaked TRX amount for a wallet address at a specified timestamp under Stake 2.0, helping determine when unstaked funds become available.

Instructions

Get the withdrawable unstaked TRX amount for an address at a given timestamp in 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": {
      "address": "<address>"
    },
    "name": "get_can_withdraw_unfreeze_amount"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesWallet address (Base58 or hex)
networkNoNetwork name. Defaults to mainnet.
timestampMsNoOptional query timestamp in milliseconds. Defaults to current time.

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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful domain context that the result is a time-specific withdrawable unstaked amount in Stake 2.0, but it does not discuss return format, error behavior, or rate limits.

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?

The definition is a single front-loaded sentence with no redundant or filler wording. Every phrase contributes to identifying the resource, the key inputs, and the Stake 2.0 context.

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 simple read-only getter with 100% schema coverage and rich annotations, the description supplies enough context to understand the operation. It could be slightly stronger by clarifying the returned unit or network behavior, but no output schema exists and the core semantics are present.

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%, so the schema already documents address, network, and timestampMs fully. The description reinforces that the address and timestamp determine the query result but adds little beyond the structured parameter documentation.

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: get the withdrawable unstaked TRX amount for an address at a timestamp in Stake 2.0. It is clear what the tool returns, though it does not explicitly distinguish itself from sibling tools such as get_available_unfreeze_count or withdraw_expire_unfreeze.

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 gives no explicit guidance on when to use this tool versus related freeze/unfreeze tools. Usage is only implied by the getter phrasing and the Stake 2.0 context, with no alternatives or exclusions named.

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