tron_mcp_server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable detailed logging | |
| NETWORK | No | Network configuration: mainnet or testnet | mainnet |
| CACHE_TTL | No | Cache time-to-live in seconds | 300 |
| PRIVATE_KEY | No | Optional private key for sending transactions (keep secure) | |
| ENABLE_CACHE | No | Enable caching for better performance | |
| FULL_NODE_URL | No | TRON full node URL | https://api.trongrid.io |
| EVENT_SERVER_URL | No | TRON event server URL | https://api.trongrid.io |
| TRONGRID_API_KEY | No | Optional TronGrid API key for higher rate limits | |
| SOLIDITY_NODE_URL | No | TRON solidity node URL | https://api.trongrid.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_balanceB | Get TRX balance for an address |
| get_account_resourcesB | Get account resources (bandwidth and energy) |
| send_trxC | Send TRX to an address |
| get_transactionC | Get transaction details by hash |
| get_blockB | Get block information with smart size management to prevent token overflow |
| get_current_block_numberA | Get current block number only (compact output) |
| contract_callC | Call a smart contract function |
| estimate_energyC | Estimate energy consumption for a contract call |
| get_java_tron_releasesC | Get latest java-tron releases from GitHub |
| search_tron_docsC | Search TRON documentation and get relevant resources |
| get_tron_referenceB | Get quick reference for TRON concepts |
| get_trx_priceA | Get current TRX price from CoinGecko |
| get_trx_market_dataB | Get detailed TRX market data |
| get_network_statisticsC | Get comprehensive TRON network statistics |
| get_energy_consumptionC | Get energy consumption statistics |
| get_defi_tvlC | Get DeFi Total Value Locked data |
| get_staking_infoB | Get TRX staking rate and information |
| get_chain_parametersC | Get current chain parameters |
| get_energy_pricesA | Get current energy and bandwidth prices |
| get_java_tron_readmeC | Get java-tron README documentation |
| get_java_tron_fileB | Get content of a specific file from java-tron repository |
| search_java_tronC | Search in java-tron repository |
| get_java_tron_structureC | Get java-tron repository structure and modules |
| get_java_tron_protosB | Get Protocol Buffer definitions from java-tron |
| get_java_tron_issuesC | Get recent issues from java-tron repository |
| estimate_contract_energyC | Estimate energy consumption for smart contract interaction using TRON node |
| batch_estimate_energyB | Batch estimate energy for multiple contract calls |
| analyze_contract_gasC | Analyze gas costs for all functions in a smart contract |
| clear_energy_cacheD | Clear energy estimation cache |
| trongrid_api_callC | Direct call to TronGrid API endpoint |
| tronscan_api_callD | Direct call to TronScan API endpoint |
| get_trongrid_blockC | Get block information directly from TronGrid API |
| get_trongrid_accountB | Get account information directly from TronGrid API |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 33 tools
Multiple tools overlap in purpose: estimate_energy and estimate_contract_energy both estimate energy costs; get_block and get_trongrid_block both retrieve block info; several java-tron tools could be consolidated. Some distinctions are clear, but an agent might struggle to choose between similar tools.
Most tools follow a verb_noun pattern (e.g., get_balance, send_trx), but there are inconsistencies like contract_call, trongrid_api_call, and analyze_contract_gas (verb_noun but with underscore). The pattern is generally readable but not uniform.
33 tools is high for a single server, but many are justified by covering different aspects of TRON. However, the inclusion of 7 java-tron-specific tools and two wrapper API calls (trongrid_api_call, tronscan_api_call) makes the set feel bloated for the core blockchain domain.
The server lacks fundamental TRON operations like token management (TRC10/TRC20), contract deployment, and account creation. It over-emphasizes java-tron repository access, which is tangential. Agents would struggle to perform common tasks without the missing operations.