get_account_resources
Destructive
Get energy and bandwidth usage and limits for a TRON account
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | TRON base58 address (starts with T) |
GoTRON MCP Server
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations state readOnlyHint=false and destructiveHint=true, while the description says 'Get', implying a read-only operation. This is a direct contradiction. No additional behavioral context is provided.
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?
The description is a single, concise sentence with no fluff. It is front-loaded with the verb and object, effectively communicating the tool's purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite being a simple getter, the description lacks output format details (e.g., units for energy/bandwidth, limits structure). With contradictory annotations and no output schema, it leaves the agent guessing about side effects and return shape.
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?
The schema already provides 100% coverage for the single 'address' parameter with its description. The tool description adds no extra meaning beyond the schema's field details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description uses specific verb 'Get' and clearly identifies the resource (energy and bandwidth usage and limits) and target (TRON account). This distinguishes it from sibling tools like get_account or get_delegated_resources.
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?
No guidance is provided on when to use this tool versus alternatives such as get_account or get_delegated_resources. It simply states what it does without any contextual or exclusionary information.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.2/5.0
Disambiguation3/5
Several tool groups have overlapping responsibilities (e.g., get_energy_prices/get_bandwidth_prices/get_chain_parameters, get_pending_transactions/get_pending_by_address/is_transaction_pending, and analyze_account vs get_account plus its resource/permission variants). These create boundary confusion despite clear descriptions, and with 43 tools an agent will likely select the wrong one occasionally.
Naming Consistency5/5
All tools follow a consistent snake_case verb_noun pattern (e.g., get_account, transfer_trx, delegate_resource, unfreeze_balance). Even the few multi-word verbs (estimate_energy, trigger_constant_contract) remain predictable. No camelCase or inconsistent verb styles.
Tool Count2/5
With 43 tools, the server is heavy. While the TRON domain is broad, the tool surface is bloated with many near-synonyms and split functionalities that could be consolidated. The rubric flags 25+ tools as too many; 43 clearly exceeds that.
Completeness3/5
The server covers a wide range of read and transaction-building operations, including staking, governance, contracts, and TRC20. However, it lacks critical lifecycle steps: there is no sign or broadcast tool, and no ability to deploy contracts or create accounts. This is a significant gap for a tool that returns unsigned transactions.