Skip to main content
Glama

undelegate_resource

Destructive

Revoke previously delegated TRON staked resources (BANDWIDTH or ENERGY) from a receiver address back to your configured wallet by specifying the receiver, amount, and resource.

Instructions

Revoke previously delegated staked resources (BANDWIDTH or ENERGY) from a receiver address back to the configured wallet.

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": {
      "receiverAddress": "<receiverAddress>",
      "amount": "<amount>",
      "resource": "<resource>"
    },
    "name": "undelegate_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesAmount of resources to revoke in Sun (1 TRX = 1,000,000 Sun)
networkNoNetwork name. Defaults to mainnet.
resourceYesResource type to revoke (BANDWIDTH or ENERGY)
receiverAddressYesThe address from which delegated resources will be revoked

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

A4.2/5.0
Behavior4/5

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

The description clarifies the intent of the action—returning the staked resources to the main wallet—which is important behavioral context. While the destructive nature is covered by the `destructiveHint` annotation, the description adds the specific goal-oriented detail of the resource returning to the configured wallet.

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 concise and highly effective. It delivers all necessary information in a single, direct sentence without any extraneous language.

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?

Given that the input schema is fully covered and annotations detail its high-risk nature, the description provides sufficient context for an agent to understand the operation. It covers the 'what' and 'who' without needing to describe return values or complex failure modes.

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?

Since schema description coverage is 100%, the description relies on defining the overall function rather than explaining individual parameter semantics. It successfully mentions the valid resource types (BANDWIDTH or ENERGY), which is already captured in the enum description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a strong, specific verb ('Revoke') and clearly identifies the resource type ('staked resources') and the direction of the transfer ('back to the configured wallet'). This clearly distinguishes the function from related delegation tools in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It defines the scope of use by stating it applies to 'previously delegated' resources. While it does not explicitly contrast with an inverse 'delegate' operation, the function name and description make the usage context very clear for an agent.

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