Skip to main content
Glama

MERX - TRON Resource Exchange

by exchange.merx

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.

Input Schema

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

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation3/5

With 66 tools, there is notable overlap between pricing tools (get_prices, get_best_price, compare_providers, get_price_history), balance/account tools (get_balance, get_account_info, get_trx_balance, get_trc20_balance), and order tools (get_order, list_orders, get_standing_order, list_standing_orders). While descriptions differentiate them, the sheer number and aliases (e.g., estimate_transaction_cost with 5 aliases) create ambiguity and potential for misselection.

Naming Consistency4/5

Naming is mostly consistent using snake_case (e.g., create_order, approve_trc20). However, there is variation in verb placement: some start with verbs (create_order, get_balance) while others with nouns (agent_status, resource_broadcast). Patterns like wait_for_delegation break the simple verb_noun structure, but overall the style is uniform.

Tool Count2/5

66 tools is far beyond typical MCP server sizes (3-15). While the domain is complex, many tools are utilities (convert_address, validate_address, explain_concept) that could be combined or omitted. The high count suggests scope creep and may overwhelm agents.

Completeness3/5

The server covers core workflows (buy resources, transfer tokens, check balances, create monitors/standing orders) but has notable gaps: order cancellation is missing (no cancel_order), many entities lack update/delete (e.g., invoices, monitors have cancel but no update), and execute_intent is not fully wired. Still, the surface is reasonably complete for its stated purpose.

Resources