Skip to main content
Glama

get_account_resource

Read-onlyIdempotent

Retrieve TRON account resource details—including energy, bandwidth, frozen balance, and delegation—for a specified address and optional network.

Instructions

Get account resource details including energy, bandwidth, frozen balance, and delegation info.

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

Input Schema

NameRequiredDescriptionDefault
addressYesAccount address (Base58 or Hex)
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds only the field-level scope, not behavioral context such as whether frozen/delegated amounts reflect pending unfreeze operations or how values are denominated. Modest added value beyond annotations.

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?

A single front-loaded sentence naming the verb and the returned data categories, with zero filler. Nothing redundant and nothing that should have been reordered.

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 two-parameter read tool with full schema coverage and complete safety annotations, the description covers the essentials. It is arguably insufficient in one respect: with no output schema, the definition says which categories appear but not their format (nested amounts, currency units, frozen-vs-delegated breakdown), which is the area an agent would most need help with.

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 address (Base58 or Hex) and network (defaults to mainnet) documented in the schema, so the baseline of 3 applies. The description contributes no additional parameter semantics beyond what the schema already provides.

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+resource ("Get account resource details") and enumerates the four data categories returned: energy, bandwidth, frozen balance, delegation info. This clearly distinguishes it from siblings like get_account_balance or get_delegated_resource, though it does not name those alternatives 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 enumerated resource fields: an agent needing staking/energy/bandwidth state would pick this. However, there is no explicit when-to-use or when-not-to-use guidance, and no routing to siblings such as get_account_balance (TRX balance) or get_delegated_resource (per-delegation detail), which overlap conceptually.

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