Skip to main content
Glama

get_delegated_resource_index

Read-onlyIdempotent

Query an account's TRON resource delegation index to identify incoming delegations from other accounts and outgoing delegations made by that account.

Instructions

Query the resource delegation index for an account: who delegated to this account, and who this account delegated to.

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_delegated_resource_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesAccount address
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 readOnly, idempotent, non-destructive, and open-world behavior. The description adds meaningful context about the index's bidirectional contents, but says nothing about return shape, pagination, or whether results are limited in size, which matters for an open-world query.

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 well-formed sentence with the key content front-loaded and no wasted words. It could be slightly tighter, 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?

With no output schema, the description should carry more of the burden of explaining what the index returns; it hints at two directions but not the record format or completeness. For a simple two-parameter read tool this is adequate but not thorough.

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 both the address and network parameters are already documented in structured fields. The description adds only that the account is the subject of the lookup, not any new semantics for address or network selection.

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 (query) and resource (resource delegation index) and clarifies the two directions of the index: incoming delegations to this account and outgoing delegations from it. This is more specific than the name alone, though it does not distinguish itself from related siblings like get_delegated_resource or get_delegated_resource_account_index_v2.

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?

The description gives no when-to-use or when-not-to-use guidance and names no alternative tool for the many closely named delegation siblings. An agent must infer from the wording alone whether this or get_delegated_resource_index_v2 style tools is appropriate.

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