@tenergy/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TENERGY_API_KEY | No | Your TEnergy API key. Used to sign requests, never shown to the model. Optional; without a key only public tools run. | |
| TENERGY_API_URL | No | API URL. Defaults to Nile testnet. Mainnet: https://api.tenergy.me/v1 with an ak_live_ key. | https://api-nile.tenergy.me/v1 |
| TENERGY_API_SECRET | No | Your TEnergy API secret. Used to sign requests, never shown to the model. Optional; without a key only public tools run. | |
| TENERGY_MCP_READ_ONLY | No | Set to 1 to remove create_quote and create_order, even with a spending key. | |
| TENERGY_MCP_MAX_ORDER_TRX | No | The most one order may cost. An order above this is refused before buying. | 50 |
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_pricesA | Read-only, free, no API key needed. Returns the current rental price table: for each resource (energy, bandwidth, activation) and tier (5m, 1h, 1d) the price in SUN per unit, min/max amount and |
| get_address_resourcesA | Read-only, free, no API key needed. Returns the on-chain energy and bandwidth an address has right now (limits, used, available) and whether it is activated. Call it before buying to see whether the address already has enough energy for its next transfer. |
| get_marketA | Read-only, free, no API key. The live energy market: every venue TEnergy reads with its 1-hour and 1-day price per unit (SUN), when it was read, and our own price. Use it to compare venues or to tell a user where energy is cheapest right now. |
| get_price_historyA | Read-only, free, no API key. Price history of one market venue (slug from get_market; "tenergy" for ours): 5-minute points of the 1-hour and 1-day price over the last N hours. |
| get_market_summaryA | Read-only, free, no API key. One month of the energy market: for each venue min / median / max price, number of readings and share of time it answered, plus the median price by hour of day (UTC). Month as YYYY-MM. |
| get_chain_parametersA | Read-only, free, no API key. The TRON fee parameters now, read from a public node: energy price (getEnergyFee, SUN per unit), bandwidth price (getTransactionFee), free bandwidth per day, unstake delay in days. |
| estimate_contract_callA | Read-only, free, no API key, nothing signed. Simulates a smart contract call on a public node (triggerconstantcontract) and returns the energy it would use and the TRX it would burn without energy. Give the function selector, e.g. "transfer(address,uint256)", and the ABI-encoded parameter hex. |
| suggest_order_sizeA | Free, offline. How much energy to order for N USDT transfers, given how many go to addresses that already hold USDT and how many to addresses with a zero USDT balance (measured 2026-09-30: 64,285 vs 130,285 energy per transfer). Use get_address_resources first to know which case a recipient is. |
| calculate_savingsB | Free. What renting energy saves versus burning TRX for USDT transfers: uses the live energy price from our price table and the chain burn price. Give transfers per day and the share that go to empty addresses. |
| get_energy_fee_historyA | Free, offline. Every approved change of the TRON energy price (getEnergyFee) since 2018 with its committee proposal and date, read from the chain on 2026-10-04. |
| explain_conceptA | Free, offline. A short, accurate explanation of a TRON resource concept for a user. Concepts: energy, bandwidth, delegation, burn, activation, recovery, rental, routing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| cheapest_energy_for_transfer | Size the energy for a transfer from the recipient, compare venues, and show burn vs rent. |
| size_batch_order | How much energy a batch of USDT payouts needs and what it saves per day. |
| explain_failed_transaction | Read a transaction by id and explain why it failed and what to do. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| energy-facts | Measured energy per USDT transfer and the energy fee history, with dates. |
| quickstart | How an agent prices, quotes and orders energy. |
| llms-txt | Index of the agent-facing documentation. |
TDQS
Scored across 11 tools
Tools mostly have distinct purposes, but get_prices and get_market both expose current energy prices, and get_price_history and get_market_summary both report market data. The descriptions clarify the differences, so confusion is limited but possible.
All tool names use snake_case with clear verb_noun patterns such as get_prices, estimate_contract_call, suggest_order_size, calculate_savings, and explain_concept. The convention is consistent and predictable throughout.
11 tools is well within the typical 3-15 range and fits the domain of TRON energy data, market info, and estimation. Each tool has a distinct function, though a few read-only queries could theoretically be consolidated.
The surface covers price data, address resources, chain parameters, estimation, savings, and concepts. However, get_prices explicitly references create_quote for binding prices, but no create_quote or order-placement tool exists, leaving a notable gap for completing a rental transaction.