Skip to main content
Glama

get_block_balance

Read-onlyIdempotent

Retrieves all balance change operations in a specified TRON block using its hash and height, helping analyze token balance movements when historical balance queries are enabled.

Instructions

Get all balance change operations in a block. Requires block hash and block number. Note: requires the node to enable historical balance query.

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": {
      "hash": "<hash>",
      "number": "<number>"
    },
    "name": "get_block_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYesBlock hash (64-char hex string)
numberYesBlock height number
networkNoNetwork name. Defaults to mainnet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / number / maximum
      Added value: +9007199254740991
  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. The description adds genuinely non-obvious behavior beyond that: it needs BOTH hash and number (not just one identifier) and will only work if the node has historical balance queries enabled, which is a real failure mode an agent must anticipate.

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?

Three short sentences, purpose front-loaded, prerequisite last. Nothing is redundant and nothing needs trimming.

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, no-output-schema tool with full schema coverage and safety annotations, the only non-structured risk is the node-configuration prerequisite, which the description covers. Return shape is left undefined but the output schema is absent, so that is a modest gap rather than a blocking one.

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%, including formats and a default for network, so the schema carries parameter meaning. The description only restates that hash and number are required and says nothing about the optional network parameter or the relationship/consistency requirement between hash and number.

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 all balance change operations in a block.' That is meaningfully narrower than the sibling get_block (block contents) or get_account_balance (account state), though it never names an alternative to sharpen the boundary.

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 resource ('in a block') and the stated requirement for hash plus number, but there is no explicit when-to-use versus sibling block/balance tools, and no guidance on what to do if the caller only has a block number.

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