Skip to main content
Glama

freeze_balance_v2

Destructive

Freeze TRX to obtain BANDWIDTH or ENERGY resources via Stake 2.0 by specifying the amount in Sun, with optional network and resource type.

Instructions

Freeze TRX to get 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": "freeze_balance_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesAmount to freeze in Sun (1 TRX = 1,000,000 Sun)
networkNoNetwork name. Defaults to mainnet.
resourceNoResource type to get. 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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true and idempotentHint=false, so the mutation and irreversibility profile is known. The description adds only the protocol label ('Stake 2.0'), not the important operational context: that frozen TRX is locked and only recoverable via an unfreeze with a waiting period, that repeated calls stack rather than replace, or that value is committed on-chain.

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 short sentence that is front-loaded on the action, with no filler or redundancy. It is efficient, though the brevity borders on under-specification rather than economy.

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 tool is simple (three parameters, no output schema, annotations covering the safety profile), so the description is close to adequate. However, for a destructive on-chain staking operation it omits what the agent most needs: lock-up/reversibility behavior and any note that the call commits irreversible value.

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%, with units (Sun), the network default and the resource enum all documented in the schema itself. The description adds no meaning beyond those fields, so the baseline of 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 names a specific verb and resource ('Freeze TRX') plus the outcome ('to get resources') and the protocol generation ('Stake 2.0'), which separates it from Stake 1.0 behavior. It does not explicitly contrast with the sibling unfreeze_balance_v2, but the directional distinction is obvious from the verb.

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 guidance, no mention of prerequisites (account must hold TRX, freezing consumes funds), and no routing to alternatives such as delegate_resource for obtaining resources from a third party. An agent must infer all selection logic from the tool name.

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