Skip to main content
Glama

get_burn_trx

Read-only

Query the total TRX burned from on-chain transaction fees since Committee Proposal No. 54 took effect, optionally selecting a network that defaults to mainnet.

Instructions

Query the total amount of TRX burned from on-chain transaction fees since No. 54 Committee Proposal took effect.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_burn_trx"
  }
}

Input Schema

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

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

Annotations already declare read-only, open-world, non-idempotent behavior, so the safety profile is covered. The description adds real substance beyond that by defining what is counted (transaction-fee burns only) and the exact historical window start, which tells the agent the result is a single cumulative snapshot rather than a per-block or per-account series.

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; the scope constraint arrives before the agent has to guess. It is dense but every clause carries information about what is being summed.

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 simple read-only aggregate with one optional parameter and no output schema, the definition covers what is measured but not how the value is returned — notably whether the number is in sun or TRX, which materially affects how an agent reports the result.

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?

Only one optional parameter exists and schema description coverage is 100%, with the mainnet default already documented. The description adds nothing about the network parameter, so this is the expected baseline rather than a strength.

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?

Clear verb (Query) plus a precisely bounded resource: total TRX burned from on-chain transaction fees, measured from the No. 54 Committee Proposal onward. The scope qualifiers make it hard to confuse with balance or block queries among the siblings, though the description never explicitly contrasts with any sibling.

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 only implied by the metric's nature — a chain-level cumulative statistic, not an account-scoped query. There is no statement of when to prefer this over a chain-parameters or fee-price tool, and no exclusions or prerequisites.

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