Skip to main content
Glama

get_account

Read-onlyIdempotent

Retrieves complete TRON account details—balance, resources, permissions, frozen balance, and votes—for a given address, with optional network selection.

Instructions

Get full account information including balance, resources, permissions, frozen balance, and votes.

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

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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the set of fields returned, with no mention of failure behavior for unknown addresses, chain-selection effects, or response shape; useful but thin beyond what annotations provide.

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 with zero filler; the field enumeration is the only extra wording and it is doing real work by signalling aggregation scope.

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 and only two well-documented parameters, the description is nearly sufficient, and listing returned facets is the right instinct. The remaining gap is disambiguation from the several sibling account read tools, which this description leaves entirely to the agent.

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%, documenting both address (Base58 or Hex) and the optional network parameter, so the baseline is 3. The description adds no additional meaning about the parameters, such as whether the address format depends on network or what the default mainnet implies.

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?

Names a specific verb and resource ("Get full account information") and enumerates the returned facets (balance, resources, permissions, frozen balance, votes), which distinguishes it from the narrower account tools. However, it never addresses the near-identical siblings get_account_info, get_account_balance, and get_account_resource, so an agent cannot tell which of these to pick from the description 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 when-to-use or when-not-to-use guidance, no mention of prerequisites, and no pointer to the more specific siblings. The word "full" hints at aggregation but the agent must infer that this is the all-in-one call versus the granular ones.

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