broadcast_transactionBroadcast 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.
| Name | Required | Description | Default |
|---|---|---|---|
| txData | Yes | Pre-signed transaction object with txID, raw_data, raw_data_hex, and signature |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the transparency burden and does well by disclosing the auto energy delegation step, payment/auth options, and the unauthenticated cost-estimate response. It does not detail every side effect or return value, but the core behavioral traits are covered beyond mere tautology.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three focused sentences present the action first, then payment modes, then unauthenticated behavior. Every sentence adds useful information, with no redundant or unnecessary wording.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is moderately complex with a nested txData object and no output schema, and the description covers auth modes and unauthenticated outputs. However, it leaves the authenticated success/response format unstated, which is a notable gap for an agent that needs to interpret the broadcast result.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already provides a 100% description coverage for txData with an explanation of the expected object fields, so the description's 'signed transaction data' adds little beyond the schema. This meets the baseline but does not add significant parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'Broadcast' and names the resource 'pre-signed TRON transaction', with the added scope 'auto energy delegation'. This clearly distinguishes it from sibling tools like broadcast_signed_permission_tx by specifying the TRON context and delegation behavior.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explains when to use the tool (when you have a signed transaction data and need energy delegation) and outlines the authentication modes (API key or x402) as well as the unauthenticated cost-estimate behavior. However, it does not explicitly name alternatives or state when not to use this tool, so it stops short of perfect guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but some overlap exists: get_prices and get_market_overview both provide pricing info, and get_available_resources, get_pool_delegations, and get_onchain_status all relate to resource status. Descriptions clarify these distinctions adequately.
Tool names follow a consistent verb_noun pattern with underscores (e.g., get_balance, register_pool, configure_auto_selling). Minor inconsistency: 'broadcast_signed_permission_tx' uses the abbreviation 'tx' while 'broadcast_transaction' uses the full word 'transaction'.
27 tools is excessive for a server with this scope, exceeding the 25-tool threshold. Several tools could be consolidated (e.g., get_prices and get_market_overview, or the various resource-status getters). The high count makes the tool surface harder to navigate.
The server covers the core domain well: registration, balance management, pool registration and configuration, energy purchase, order tracking, swap, and voting. Minor gaps exist, such as no explicit tool for configuring auto actions (stake/claim) or cancelling orders, but these do not severely hinder core workflows.