Skip to main content
Glama

broadcast_hex

Destructive

Submit a signed, protobuf-encoded transaction hex string to the TRON network to execute prepared on-chain transactions.

Instructions

Broadcast a signed, protocol buffer-encoded transaction hex string to the TRON network.

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": {
      "transaction": "<transaction>"
    },
    "name": "broadcast_hex"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.
transactionYesSigned transaction hex string

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.1.7

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is largely covered. The description adds the useful precondition that the hex must be signed, but says nothing beyond that about irreversibility, duplicate submission, or error outcomes for a destructive non-idempotent write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tightly written sentence with the action and resource front-loaded and no redundant wording. Every clause earns its place.

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 two-parameter, no-output-schema tool the description covers the essentials of what is being broadcast and where. However, for a destructive, non-idempotent network broadcast it omits what happens on rejection, that resubmission is unsafe, and how the result is reported.

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%, so both parameters (transaction, network) are already documented in the schema. The description adds only the qualifier that the hex is signed and protobuf-encoded, which the schema's 'Signed transaction hex string' already conveys. 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 states a specific verb (broadcast), a specific resource (a signed, protobuf-encoded transaction hex string) and the target network (TRON). An agent can grasp the operation immediately. It does not differentiate from the sibling broadcast_transaction, which likely overlaps, so it falls short of a 5.

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?

Usage is only implied: the word 'signed' signals the prerequisite that a transaction must already be created and signed before calling this. There is no explicit statement of when to use this versus broadcast_transaction, no mention of failure behavior or retry, and no note that broadcast is final/irreversible.

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

Deploy Server

Other Tools