Skip to main content
Glama
Sign In

MERX - TRON Resource Exchange

by exchange.merx
OverviewDiscussionsAdmin

get_best_price

Read-onlyIdempotent

Get the exact executable MERX quote and quoted provider. Requires resource, amount, a fixed-grid duration, and target_address.

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": {
      "resource": "<resource>",
      "amount": "<amount>",
      "duration": "<duration>",
      "target_address": "<target_address>"
    },
    "name": "get_best_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesAmount of resource units needed.
durationYesExact rental duration in seconds on the fixed grid, from 2 minutes through 24 hours.
resourceYesResource type.
target_addressYesTRON recipient address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / duration / description
      Previous value: -"Exact rental duration in seconds."New value: +"Exact rental duration in seconds on the fixed grid, from 2 minutes through 24 hours."
  2. Changed3 schema fields changed
    • addedInput schema / properties / duration
      Added value: +{
+  "description": "Exact rental duration in seconds.",
+  "enum": [
+    120,
+    300,
+    600,
+    900,
+    1800,
+    3600,
+    10800,
+    21600,
+    86400
+  ],
+  "type": "number"
+}
    • addedInput schema / properties / target_address
      Added value: +{
+  "description": "TRON recipient address.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "resource"
-]New value: +[
+  "resource",
+  "amount",
+  "duration",
+  "target_address"
+]
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that the result is an 'exact executable quote' with the quoting provider, but says nothing about quote lifetime/expiry or failure modes, which matter for an execution-ready quote.

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

Conciseness4/5

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

Two short sentences with the outcome stated first and prerequisites second; no filler. Slightly reduced because the second sentence is essentially a restatement of the schema's required list.

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?

With no output schema, the description must convey the return shape, and 'exact executable MERX quote and quoted provider' is only a high-level sketch — no indication of price fields, expiry, or what makes the quote executable. Adequate but leaves real gaps for a tool whose whole value is the returned quote.

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% and both enums are documented inline, so the baseline of 3 applies. The description reinforces the 'fixed-grid duration' constraint and target_address requirement, but adds no syntax or constraint detail beyond the schema.

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?

States a specific verb and resource ('Get the exact executable MERX quote and quoted provider'), and the qualifier 'executable' separates it from advisory siblings like analyze_prices or compare_providers. It never names those siblings explicitly, so a small differentiation gap remains.

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?

The description lists the four required inputs but gives no when-to-use guidance, no exclusions, and no pointer to alternatives such as get_swap_quote or compare_providers. Usage is only implied by the fact that a quote is executable.

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