powersun-tron-mcp

Estimate Cost

estimate_cost

Calculate the cost of purchasing TRON Energy or Bandwidth. Exact resourceAmount takes priority. Derived Bandwidth is an estimate for standard USDT TRC-20 transfers (345 units plus 5%); other transaction templates require an explicit resourceAmount. Minimum order sizes still apply.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "txCount": "<txCount>"
    },
    "name": "estimate_cost"
  }
}

Input Schema

Name	Required	Description
`txType`	No	Transaction type (default: trc20_transfer). trc20_transfer_new = first-time transfer to an address.
`txCount`	Yes	Number of transactions
`resourceType`	No	Resource type (default: ENERGY)
`targetAddress`	No	TRON target address. Required for an executable market quote.
`resourceAmount`	No	Exact resource amount; otherwise derived from transaction count.
`durationMinutes`	No	Duration in minutes. Allowed: 2, 5, 10, 15, 30, 60, 180, 360, 1440, 10080, 43200. Default: 60.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 7, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / resourceAmount / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / txCount / maximum
```
Added value: +9007199254740991
```

Changed3 schema fields changedOct 22, 2026

changedInput schema / properties / durationMinutes / description

Previous value: -"Duration in minutes. Allowed: 2, 5, 10, 15, 30, 60, 360, 1440, 10080, 43200. Default: 60."New value: +"Duration in minutes. Allowed: 2, 5, 10, 15, 30, 60, 180, 360, 1440, 10080, 43200. Default: 60."

addedInput schema / properties / resourceAmount

Added value: +{
+  "description": "Exact resource amount; otherwise derived from transaction count.",
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / targetAddress

Added value: +{
+  "description": "TRON target address. Required for an executable market quote.",
+  "type": "string"
+}

First observedFeb 26, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose real behavior: derivation math (345 units plus 5% per standard USDT TRC-20 transfer), priority of resourceAmount, and that minimum order sizes still apply. It does not state that this is a non-mutating estimate with no side effects, whether the quote expires, or how prices are sourced.

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?

Four short sentences, front-loaded with the purpose, then the precedence rule, then the derivation caveat. Dense but every sentence conveys an operational constraint; no filler.

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?

With no output schema, the description should say what a cost estimate looks like (currency unit, whether it includes fees, per-unit vs total). It never addresses the return value at all, which is the tool's whole output, leaving a notable gap for a 6-parameter pricing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: it explains the interaction between resourceAmount and the transaction-derived amount, and constrains which txType templates can use derived bandwidth. That is context the schema descriptions alone do not spell out.

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?

States a specific verb and resource: 'Calculate the cost of purchasing TRON Energy or Bandwidth.' This implicitly separates it from the mutating sibling buy_energy, so an agent can tell a quote from a purchase, though no sibling is named outright.

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?

The description gives conditional guidance (exact resourceAmount takes priority; other transaction templates require an explicit resourceAmount), which effectively tells the caller how to drive the tool. It never states when to use this versus alternatives like get_market_overview, get_prices, or buy_energy, nor any prerequisites such as needing a targetAddress for an executable quote.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All powersun-tron-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.