Skip to main content
Glama

MERX - TRON Resource Exchange

by exchange.merx

get_best_price

Read-onlyIdempotent

Quick lookup of the single cheapest provider for a resource type, with optional minimum amount filter. CAVEAT: this returns a single representative price per provider, not broken down by duration tier — short rentals (5min) and long rentals (30 days) have very different per-unit prices and this tool does not distinguish between them. For an accurate per-tier comparison, use get_prices(duration=N) where N is the exact rental duration in seconds (e.g. 3600 for 1h, 86400 for 1d, 2592000 for 30d). Use get_best_price only when you need the absolute floor price as a quick sanity-check. No auth required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountNoAmount of resource units needed.
resourceYesResource type.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description's main value is adding the caveat that the tool returns a single representative price per provider and does not break down by duration tier. It also explicitly states 'No auth required,' which is a useful behavioral detail beyond the 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 and front-loaded with the core purpose. It includes a caveat and alternative guidance in a compact form. Each sentence earns its place, and the use of examples for duration values enhances clarity without unnecessary verbosity.

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?

Given the tool's simplicity (2 params, no output schema), the description covers purpose, limitations, auth requirements, and alternative tool guidance. It fully equips the agent to decide when to use this tool and what to expect, making it contextually complete.

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 coverage is 100%, providing baseline 3. The description adds meaningful context by describing 'amount' as an 'optional minimum amount filter,' clarifying its role beyond the schema's 'Amount of resource units needed.' This helps the agent understand that amount is a filter criterion, not a quantity to be purchased.

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's purpose: quick lookup of the single cheapest provider for a resource type, with an optional minimum amount filter. It uses specific verbs and resources, and explicitly distinguishes itself from the sibling tool get_prices by contrasting their use cases.

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?

The description gives explicit guidance on when to use this tool versus alternatives: 'Use get_best_price only when you need the absolute floor price as a quick sanity-check' and recommends get_prices(duration=N) for accurate per-tier comparison. It also explains the caveat about duration tiers, preventing misuse.

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