Skip to main content
Glama

delegate_resource

Destructive

Delegate staked BANDWIDTH or ENERGY from your configured TRON wallet to another address, with optional lock period for non-revocable delegation.

Instructions

Delegate staked resources (BANDWIDTH or ENERGY) from the configured wallet to another address.

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

Input Schema

NameRequiredDescriptionDefault
lockNoWhether the delegation is locked (non-revocable within the lock period). Defaults to false.
amountYesAmount of resources to delegate in Sun (1 TRX = 1,000,000 Sun)
networkNoNetwork name. Defaults to mainnet.
resourceYesResource type to delegate (BANDWIDTH or ENERGY)
lockPeriodNoLock period in blocks when lock is true. Ignored if lock is false. Defaults to 0.
receiverAddressYesThe address that will receive the delegated resources

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

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the risk profile is covered structurally. The description adds one piece of context beyond that — that the source is the 'configured wallet' rather than a caller-supplied account. It does not address revocability, the effect of lock/lockPeriod, or whether the operation broadcasts a transaction.

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, naming the verb, the resource set, the source and the destination. It is terse enough to be efficient, though it leaves no room for the risk/prerequisite framing that would make it stronger.

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 six-parameter mutation with full schema coverage and annotations that carry the destructive/non-idempotent profile, the description covers what the tool does and where funds come from. Missing are prerequisites (wallet configured, enough staked resources) and the lock irreversibility consequence, which is delegated to the schema field text.

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 all six parameters (amount in Sun, receiverAddress, resource enum, lock, lockPeriod, network) are already documented at the field level. The description only restates the resource enum values and adds no format or constraint detail beyond the schema, 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?

States a specific verb ('Delegate') plus the resource ('staked resources BANDWIDTH or ENERGY') and the direction ('from the configured wallet to another address'). It is clearly distinguishable from undelegate_resource and the get_delegated_resource* readers, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the verb: use this to move staked bandwidth/energy to another address. There is no explicit when-to-use/when-not, no mention of prerequisites (a configured, funded wallet with sufficient staked resources), and no pointer to undelegate_resource as the inverse operation.

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