Skip to main content
Glama

get_account_balance

Read-onlyIdempotent

Retrieve the TRX balance for a TRON account at a specified block height and hash, enabling balance checks tied to a precise on-chain snapshot.

Instructions

Get account TRX balance at a specific block height.

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>",
      "blockHash": "<blockHash>",
      "blockNumber": "<blockNumber>"
    },
    "name": "get_account_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesAccount address (Base58)
networkNoNetwork name. Defaults to mainnet.
blockHashYesBlock hash (hex string)
blockNumberYesBlock number

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 readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds only the TRX-specific, block-pinned scope; it says nothing about behavior for unknown addresses, pruned blocks, or the shape/units of the returned balance, so extra value beyond annotations is modest.

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 front-loaded sentence with no filler or redundancy. It is efficient, though its terseness leaves the scoping qualifier doing more work than one clause can bear.

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?

For a read-only getter with a fully described schema and rich annotations, no output schema needed, the description covers the essential what and scope. The remaining gap is disambiguation among the several similarly named balance tools, which is a real but limited omission.

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%, so all four parameters are already documented in the schema. The description adds no meaning beyond that, notably not explaining why both blockHash and blockNumber are required together or how network defaults interact. Baseline 3 applies when the schema carries the load.

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 account TRX balance') plus a scope qualifier ('at a specific block height'), which distinguishes it from a plain latest-balance getter. It does not name the near-identical siblings get_balance or get_block_balance, so an agent must infer the split from the qualifier alone.

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 block-height phrasing implies the use case (historical/pinned balance queries) without ever stating when to prefer this over get_balance or get_block_balance, and gives no prerequisites or exclusions. Usage is inferable but not guided.

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