TronEnergyFrog
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRONENERGYFROG_API_KEY | No | Optional account API key from @tron_energy_frog_bot; enables account tools. | |
| TRONENERGYFROG_EVM_PRIVATE_KEY | No | Optional Base wallet key that pays x402 quotes in USDC. | |
| TRONENERGYFROG_MAX_PAYMENT_USD | No | Per-payment USDC cap for pay_x402_quote. Default 5. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
TronEnergyFrog rents TRON Energy so USDT TRC-20 transfers do not burn TRX. Energy goes to the wallet that SENDS the USDT. Use 65,000 Energy when the recipient already holds USDT and 130,000 when it does not. Always confirm address, amount and price with the user before a tool that spends money.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_energy_pricesA | Live TronEnergyFrog prices for 65,000 and 130,000 TRON Energy, for 1 hour or 1 day, compared with the TRX the network would burn without Energy. No API key needed. |
| create_x402_quoteA | Locks a TRON Energy rental price for 10 minutes, payable in USDC on Base (or Solana) through x402. No account or API key. Energy is delegated to target_address, which must be the wallet that will SEND the USDT. Creating a quote costs nothing. |
| get_x402_rentalB | Payment and delivery status of an x402 quote: payment_required, settling, fulfillment_pending, succeeded, failed or expired. |
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 3 tools
Each tool covers a clearly distinct step: reading prices, creating a locked quote, and checking that quote's status. There is no meaningful overlap or risk of misselection.
All three follow a consistent verb_noun snake_case pattern (get_energy_prices, create_x402_quote, get_x402_rental). The x402 prefix groups related quote operations predictably.
Three tools is exactly right for a focused energy-pricing and rental-quote service. Every tool earns its place in the workflow and no superfluous operations are exposed.
The core lifecycle is covered: check prices, create a quote, and poll payment/fulfillment status. Minor gaps exist around quote management (listing or cancelling quotes, refund handling), but these are not essential to the primary flow.