Skip to main content
Glama

MERX - TRON Resource Exchange

by exchange.merx

estimate_transaction_cost

Read-onlyIdempotent

Estimate cost of a TRON transaction BEFORE sending. Aliases: estimate_cost, calculate_cost, transaction_cost, energy_cost, transfer_cost. Calculate exactly how much energy, bandwidth, and TRX a TRON transaction will cost before sending it. Use this to answer questions like "how much does a USDT transfer cost?" or "what will it cost me to send 100 USDT to address X?". Returns: energy units needed, bandwidth needed, TRX cost if you burn directly, and TRX cost if you rent energy from Merx (typically 70-80% cheaper). Supports trc20_transfer (e.g. USDT/USDC), trc20_approve, trx_transfer, and custom contract calls. No auth required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountNoToken amount (as string).
operationYesTransaction type.
parameterNoABI-encoded parameter (custom).
to_addressNoRecipient TRON address.
from_addressNoSender TRON address.
token_addressNoTRC20 contract address.
contract_addressNoContract address (custom).
function_selectorNoFunction selector (custom).

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly and idempotent hints. The description adds valuable behavioral context by detailing the exact return values (energy, bandwidth, TRX costs, rental cost comparison) and noting no auth is required, going beyond what annotations provide.

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 and front-loaded, starting with the core purpose. Each sentence adds value: aliases, exact costing, examples, return breakdown, supported operations, and auth status. No redundancy or filler.

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

Completeness4/5

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

Without an output schema, the description effectively explains return values and covers key aspects like supported operations and cost-saving differences. It is complete enough for an agent to invoke correctly, though it does not enumerate all edge cases or parameter combinations, which the schema partially handles.

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 coverage is 100% with all parameters described. The description adds minimal parameter-specific semantics beyond the schema, but its mention of supported operation types and custom contract calls indirectly enriches understanding of related parameters, meeting the baseline for high schema coverage.

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 clearly states the tool estimates TRON transaction costs before sending, with a specific verb and resource. It distinguishes itself from siblings like estimate_contract_call by listing supported operation types and explicitly framing it as a pre-send cost estimator with aliases.

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?

Provides clear usage context with example questions and supported operation types, implicitly guiding when to use it. However, it does not explicitly contrast with the sibling tool estimate_contract_call, so exclusion guidance is missing.

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