Skip to main content
Glama

get_delegated_resource_v2

Read-onlyIdempotent

Fetch delegated bandwidth and energy details between two TRON addresses under Stake 2.0 to verify delegation status.

Instructions

Get delegated resource details (bandwidth and energy) between two addresses under 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": {
      "fromAddress": "<fromAddress>",
      "toAddress": "<toAddress>"
    },
    "name": "get_delegated_resource_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.
toAddressYesDelegatee address (Base58 or hex)
fromAddressYesDelegator address (Base58 or hex)

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, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful substance beyond that by naming the two resource types measured (bandwidth and energy) and the Stake 2.0 context, but it says nothing about response shape, zero/empty delegation behavior, or network-dependent results.

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 wasted wording; the purpose and the resource types come first. It could have used the remaining space for routing guidance rather than stopping short, but nothing is redundant.

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?

This is a simple read-only query whose schema is fully documented, so the description is nearly adequate. However, with no output schema, it should have specified what the returned 'details' look like (e.g. delegated/available amounts), and it omits how this differs from the other delegated-resource siblings.

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 both addresses and the optional network parameter documented in the schema itself. The description only echoes that there are two addresses and does not clarify address roles (delegator vs delegatee) beyond what the schema already states, 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 gives a specific verb and resource ('Get delegated resource details') and scopes it to bandwidth and energy between two addresses under Stake 2.0. It is clear what the tool returns, but it never differentiates itself from the closely named siblings get_delegated_resource and get_delegated_resource_account_index_v2, leaving the agent to infer the distinction from the version suffix alone.

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 explicit when-to-use guidance and no named alternative, despite several sibling tools covering overlapping delegated-resource queries (index, account index, v1 variants). The 'under Stake 2.0' phrasing implies scope but does not tell the agent when this is the right call versus those siblings.

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