powersun-tron-mcp

Broadcast Transaction

broadcast_transaction

Broadcast a pre-signed TRON transaction with auto energy delegation. Send your signed transaction data and PowerSun will delegate energy before broadcasting. Works with API key (balance deduction) or x402 USDC payment. Without authentication, returns cost estimate.

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": {
      "txData": "<txData>"
    },
    "name": "broadcast_transaction"
  }
}

Input Schema

Name	Required	Description	Default
`txData`	Yes	Pre-signed transaction object with txID, raw_data, raw_data_hex, and signature

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 7, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- changedInput schema / properties / txData / additionalProperties
```
Previous value: -trueNew value: +{}
```
- changedInput schema / properties / txData / required
```
Previous value: -[
-  "txID"
-]New value: +[
+  "txID",
+  "raw_data"
+]
```

Changed5 schema fields changedFeb 26, 2026

addedInput schema / properties / txData / additionalProperties
```
Added value: +true
```

addedInput schema / properties / txData / properties

Added value: +{
+  "raw_data": {},
+  "raw_data_hex": {
+    "maxLength": 100000,
+    "type": "string"
+  },
+  "signature": {
+    "items": {
+      "maxLength": 200,
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "txID": {
+    "maxLength": 64,
+    "type": "string"
+  }
+}

addedInput schema / properties / txData / required
```
Added value: +[
+  "txID"
+]
```
addedInput schema / properties / txData / type
```
Added value: +"object"
```
addedInput schema / required
```
Added value: +[
+  "txData"
+]
```

First observedFeb 26, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations at all, the description carries the full burden and does deliver real behavioral facts: energy is delegated before broadcasting, billing differs by auth mode, and unauthenticated calls return an estimate rather than performing the write. However, it never states that a broadcast is an irreversible on-chain mutation, nor anything about failure modes such as an expired or already-broadcast transaction, which are the traits an agent most needs to avoid a bad call.

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?

Three short sentences, front-loaded with the action and the automatic delegation behavior, then payment modes, then the unauthenticated fallback. There is mild redundancy between 'Broadcast a pre-signed TRON transaction' and 'Send your signed transaction data', but nothing is wasted or buried.

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?

For a nested-object, single-parameter mutation tool with no annotations and no output schema, the definition covers the billing and delegation story but leaves the agent guessing about the response (does it return a txID, a receipt, a status?) and about error behavior. Adequate but with clear gaps given how much structured metadata is absent.

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?

Schema description coverage is 100% and the nested txData object documents txID, raw_data, raw_data_hex, and signature, so the structured data already does the work. The description only says 'send your signed transaction data', adding no format, encoding, or size guidance beyond what the schema supplies — baseline 3 applies.

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?

The description gives a specific verb and resource — 'Broadcast a pre-signed TRON transaction' — plus the distinguishing twist that energy delegation happens automatically before broadcast. It is clear what the tool does, but it never contrasts itself with the sibling 'broadcast_signed_permission_tx', so an agent must infer the boundary between the two broadcast tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is genuinely useful: it states the two payment paths (API key with balance deduction, or x402 USDC) and that an unauthenticated call returns a cost estimate instead of broadcasting, which tells an agent it can safely probe pricing first. What is missing is any explicit when-to-use-this-vs-that guidance against the sibling broadcast tool, and no stated prerequisite that the transaction must already be signed and unexpired.

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.