Skip to main content
Glama

get_delegated_resource

Read-onlyIdempotent

Query how many resources one TRON account has delegated to another under Stake 2.0 using delegator and recipient addresses.

Instructions

Query the amount of resources delegated from one account to another (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"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.
toAddressYesRecipient address
fromAddressYesDelegator address

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 versioning context ('Stake 2.0'), which likely explains which delegation mechanism is queried, but it says nothing about return shape, resource units, or behavior for unknown addresses.

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?

One short sentence with no filler and the key qualifier ('Stake 2.0') placed at the end. There is no wasted wording, though there is also no structural layering to speak of.

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?

For a three-parameter read-only query with full schema coverage and annotations, the description covers the essentials. However, for a tool in a dense family of near-identically named variants, it omits the one thing an agent most needs: how this differs from the v2/index 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%, so network, toAddress, and fromAddress are all documented in the schema; baseline 3 applies. The description's 'from one account to another' loosely maps onto the from/to parameters but adds no syntax, format, or default information beyond the schema.

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 ('Query the amount of resources delegated') plus a direction ('from one account to another') and version context ('Stake 2.0'). This is clear enough to act on, but it does not distinguish it from the very similar siblings get_delegated_resource_v2 and get_delegated_resource_index.

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 or when-not-to-use guidance, and no mention of the closely named alternatives (v2, index, account_index_v2) in the sibling set. The only contextual hint is the 'Stake 2.0' parenthetical, which implies version-dependent routing but leaves the agent to infer it.

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