MERX - TRON Resource Exchange

create_order

Idempotent

Buy energy or bandwidth at the Merx market quote. Confirmed Merx funds and API key required; no commission.

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_type": "<resource_type>",
      "amount": "<amount>",
      "duration_sec": "<duration_sec>",
      "target_address": "<target_address>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_order"
  }
}

Input Schema

Name	Required	Description
`amount`	Yes	Amount of resource units (min 65000 for ENERGY, 1000 for BANDWIDTH).
`duration_sec`	Yes	Rental duration in seconds on the fixed market grid, from 2 minutes through 24 hours.
`max_price_sun`	No	Optional offered price in SUN/unit. Below-current offers fail; equal or higher offers execute at the submitted price. Omit to use the current best price.
`resource_type`	Yes	Resource type to purchase.
`target_address`	Yes	TRON address to receive delegated resources.
`idempotency_key`	Yes	Unique operation ID (1–200 characters). Reuse this exact value when retrying after a timeout or lost response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 22, 2026

changedInput schema / properties / amount / description

Previous value: -"Amount of resource units (min 65000 for ENERGY, 300 for BANDWIDTH)."New value: +"Amount of resource units (min 65000 for ENERGY, 1000 for BANDWIDTH)."

changedInput schema / properties / duration_sec / description

Previous value: -"Rental duration in seconds (e.g. 300, 3600, 86400, 2592000)."New value: +"Rental duration in seconds on the fixed market grid, from 2 minutes through 24 hours."

addedInput schema / properties / duration_sec / enum

Added value: +[
+  120,
+  300,
+  600,
+  900,
+  1800,
+  3600,
+  10800,
+  21600,
+  86400
+]

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "Unique operation ID (1–200 characters). Reuse this exact value when retrying after a timeout or lost response.",
+  "type": "string"
+}

changedInput schema / properties / max_price_sun / description

Previous value: -"Optional max price in SUN/unit. Order fails if no provider is cheaper."New value: +"Optional offered price in SUN/unit. Below-current offers fail; equal or higher offers execute at the submitted price. Omit to use the current best price."

addedInput schema / properties / max_price_sun / multipleOf
```
Added value: +0.001
```

changedInput schema / required

Previous value: -[
-  "resource_type",
-  "amount",
-  "duration_sec",
-  "target_address"
-]New value: +[
+  "resource_type",
+  "amount",
+  "duration_sec",
+  "target_address",
+  "idempotency_key"
+]

First observedMar 31, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare it is a non-read-only, idempotent, non-destructive mutation, and the description adds meaningful context on top: wallet funds must be confirmed, an API key is needed, and no commission is charged. It stops short of describing what happens on partial failure or what the call returns, but with annotations covering the safety profile this is solidly above baseline.

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?

A single compact sentence with the action front-loaded and the prerequisites appended; every clause carries information (venue, funds requirement, auth, cost) with no filler.

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 6 parameters, 100% schema coverage, and annotations, the input side is well covered. However, there is no output schema and the description never indicates what a successful call yields (e.g., an order ID to use with get_order or wait_for_delegation), which is a real gap for a purchase tool.

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 description coverage is 100% and the property descriptions cover minimums, the duration enum grid, and the exact max_price_sun execution semantics in detail. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 ('Buy energy or bandwidth') plus the venue ('Merx market quote'), so the agent knows exactly what the tool does. It does not, however, distinguish itself from siblings that also acquire resources (ensure_resources, create_paid_order, create_standing_order), leaving overlap to inference.

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?

Prerequisites are stated clearly ('Confirmed Merx funds and API key required; no commission'), which is useful context for when a call will succeed. But there is no explicit guidance on choosing this over a paid order, a standing order, or ensure_resources, so routing among the acquisition siblings remains implied.

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 tools Inspect

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.