Skip to main content
Glama

get_account_info

Read-onlyIdempotent

Retrieve a TRON account's TRX and TRC20 balances, frozen resources, and votes from TronGrid indexed data to inspect wallet holdings and staking status.

Instructions

Get comprehensive account information from TronGrid indexed data, including TRX balance, TRC20 balances, frozen resources, and votes. Data comes from the TronGrid indexer and may have slight delays compared to on-chain state.

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

Input Schema

NameRequiredDescriptionDefault
addressYesAccount address (base58 T-address or hex 41-prefixed)
networkNoNetwork name. Defaults to mainnet.
onlyConfirmedNoOnly return confirmed data

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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context: the data is indexer-derived and can be slightly stale relative to chain state. It stops short of describing pagination or response shape, but no output schema exists to lean on.

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?

Two sentences, no filler. The scope enumeration is front-loaded and the staleness caveat follows directly as a consequence of the stated data source.

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?

With no output schema, the description usefully enumerates the categories of data returned, which is the main thing an agent needs here. Minor gaps remain around response shape and error cases (e.g., address not found), but the core call decision is well supported.

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 coverage is 100% and each of the three parameters (address format, network default, onlyConfirmed) is documented in the schema itself. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the work.

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 and resource ('Get comprehensive account information') and enumerates the returned data classes (TRX balance, TRC20 balances, frozen resources, votes). This distinguishes it in spirit from narrower siblings like get_account_balance or get_account_trc20_balances, but it never names them, so differentiation requires inference.

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?

The note that data comes from the TronGrid indexer and may lag on-chain state implies when this tool is and isn't appropriate, but the agent must infer the alternative (a direct on-chain lookup such as get_account). No explicit when-to-use or when-not-to-use instruction is given.

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