Skip to main content
Glama
Sign In

MERX - TRON Resource Exchange

by exchange.merx
OverviewDiscussionsAdmin

resource_broadcast

Destructive

Broadcast a signed TRON transaction with automatic energy optimization. If the target address lacks sufficient energy, MERX purchases the deficit at the best market price before broadcasting. One call: estimate, buy energy, wait for delegation, broadcast.

Requires MERX_API_KEY with the "broadcast" scope, and a pre-signed transaction. Returns txid on success, refunds on timeout.

NOTE: This endpoint is currently behind a feature flag and disabled by default in production. If you get a 503 MAINTENANCE error, use the manual flow instead: call ensure_resources to provision energy, then sign and broadcast the transaction with your own TronWeb client.

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": {
      "signed_tx": "<signed_tx>",
      "target_address": "<target_address>"
    },
    "name": "resource_broadcast"
  }
}

Input Schema

NameRequiredDescriptionDefault
signed_txYesHex-encoded signed TRON transaction
target_addressYesTRON address that will execute the transaction (must match TX sender)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Discloses the multi-step behavior (energy purchase, waiting, broadcasting), the success return (txid), the timeout refunds, and the feature-flag status. Annotations already mark it destructive, and the description adds rich context without contradicting annotations.

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?

The description is well-structured with three short paragraphs: behavior, requirements/returns, and fallback. Every sentence earns its place, providing necessary operational detail without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description clearly states the success output (txid), timeout behavior (refunds), and failure fallback. It covers prerequisites, trigger conditions, and alternative flows, making it fully contextual for an agent.

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 covers both parameters with descriptions (signed_tx, target_address). The description adds operational meaning by explaining that the target_address is the one checked for energy sufficiency and that the transaction must be pre-signed, which is not fully captured in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Broadcast a signed TRON transaction with automatic energy optimization.' It clearly differentiates from siblings by describing its unique all-in-one flow (estimate, buy energy, wait, broadcast) and explicitly contrasts with the manual flow using ensure_resources.

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

Usage Guidelines5/5

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

Provides explicit when-to-use context: requires a pre-signed transaction and an API key with 'broadcast' scope. It also gives a concrete when-not-to-use scenario, including a fallback manual flow via ensure_resources and TronWeb if a 503 error occurs.

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

All MERX - TRON Resource Exchange toolsInspect
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.

Resources