Skip to main content
Glama

get_available_unfreeze_count

Read-onlyIdempotent

Returns the number of remaining available unstake (unfreeze) operations for a TRON address under Stake 2.0, so you can check how many unfreezes are still allowed.

Instructions

Get remaining available unstake (unfreeze) operations for an address 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_available_unfreeze_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesWallet address (Base58 or hex)
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds genuine context with 'remaining available' and the Stake 2.0 scope, signalling this is a quota/capacity read rather than a balance. It does not explain what the count is bounded by (e.g. a max pending-unfreeze limit) or how it changes with pending operations.

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 no filler; the scope qualifier 'in Stake 2.0' arrives where it matters. Slightly more than bare minimum would be welcome, but nothing is 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?

For a simple read-only count query with rich annotations and a fully described schema, the description is nearly sufficient. The main gap is that there is no output schema and the description never says the result is a numeric remaining-operations count, which an agent must infer.

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 coverage is 100%, so both 'address' (Base58 or hex) and 'network' (defaults to mainnet) are fully documented in the schema. The description only reinforces the address scoping and adds the Stake 2.0 context; it says nothing about the network parameter, so baseline 3 applies.

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 gives a specific verb and resource ('Get remaining available unstake (unfreeze) operations') and scopes it to 'an address in Stake 2.0', which is precise enough to distinguish it from generic account getters like get_account. It does not explicitly separate itself from close siblings such as get_can_withdraw_unfreeze_amount or unfreeze_balance_v2, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus alternatives (e.g. as a precondition check before unfreeze_balance_v2) and no exclusions. The only implicit signal is the word 'remaining', which hints at quota checking but is not spelled out.

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