Tronsave MCP Testnet

Create Order

tronsave_create_order

Create a new buy order on the TronSave market. Key inputs: orderResourceType (ENERGY|BANDWIDTH), orderReceiver (TRON base58), orderUnitPrice in SUN (NOT TRX), orderDurationSec, orderResourceAmount, and paymentMethod: (1) onchain — requires a signed payment tx in paymentSignedTx; (2) internal — deducts from internal balance. Side effect: creates a live order matchable by the market. Requires a signature session and mcp-session-id. Always derive orderUnitPrice and paymentPaymentAmount from the latest tronsave_estimate_buy_resource for the same receiver, amount, and duration to avoid reverts. FRESHNESS: re-quote immediately before submitting — estimates older than a few seconds (one TRON block ≈ 3s) may be stale and cause the order to revert or fill at the wrong price.

Input Schema

TableJSON Schema

Name	Required	Description
`orderReceiver`	Yes	TRON base58 address (starts with T) that receives delegated resource. Same as `receiver` passed to `tronsave_estimate_buy_resource`.
`paymentMethod`	Yes	Payment method for this order: `onchain` (wallet signed tx) or `internal` (internal balance).
`orderUnitPrice`	Yes	Unit price in SUN. Prefer aligning with `minResourcePrice` or `buyResourcePrice` from the latest `tronsave_estimate_buy_resource` for the same receiver, amount, and duration.
`paymentSignedTx`	No	Required when `paymentMethod=onchain`. TronWeb-shaped signed TRON transaction (`{ txID, raw_data, raw_data_hex, signature[] }`). Must be produced client-side by the user's wallet; never fabricate or hand-edit.
`orderDurationSec`	Yes	Delegation duration in seconds. Must match the `durationSec` used in `tronsave_estimate_buy_resource`.
`orderResourceType`	Yes	Resource to buy: ENERGY (smart contracts) or BANDWIDTH (transactions). Must match `tronsave_estimate_buy_resource`.
`orderResourceAmount`	Yes	Amount of ENERGY or BANDWIDTH units to purchase. Same as `buyResourceAmount` in estimate when applicable.
`paymentPaymentAmount`	Yes	Payment amount in SUN. Prefer deriving from `tronsave_estimate_buy_resource`; if converting to TRX, divide SUN by `1e6`.

Output Schema

TableJSON Schema

Name	Required	Description
`code`	Yes	GraphQL mutation status code (HTTP-like; `0`/`200` indicates success). Always pair with `success` for routing.
`data`	No
`message`	Yes	Human-readable status text. Populated even on success; localized error messages may appear here on failure.
`success`	Yes	Whether the mutation succeeded at the backend level. Always check this before reading `data`.

TDQS

A4.3/5.0

Behavior4/5

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

Annotations indicate non-read-only and non-idempotent. The description confirms the side effect (creates a live order), requires a signature session, and warns about staleness. It adds context beyond annotations without contradiction.

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?

The description is moderately long but well-structured, starting with purpose, then key inputs, side effect, and important usage notes. It could be slightly more concise, but all information is relevant and front-loaded.

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?

Given the complexity (8 parameters, nested objects, two payment methods), the description covers the workflow, prerequisites, and freshness requirement. It references the estimate tool for parameter derivation. While output is not described, an output schema exists, so this is acceptable.

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%, but the description adds value by linking orderUnitPrice and paymentPaymentAmount to the estimate tool, explaining the consistency needed with estimate parameters, and clarifying payment method semantics. This goes beyond the schema definitions.

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 explicitly states it creates a new buy order on the TronSave market. It lists key inputs and the side effect of creating a matchable order. The verb 'create' aligns with the tool name, and the resource 'buy order' is clearly defined. While sibling tools exist, the purpose is specific and unambiguous.

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?

The description provides clear guidance on deriving parameters from tronsave_estimate_buy_resource to avoid reverts, and explains the two payment methods and their requirements. It also warns about freshness. However, it does not explicitly state when to use this tool versus alternatives like tronsave_cancel_order or tronsave_update_order.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Tronsave MCP Testnet tools Inspect

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

A3.8/5.0

Disambiguation2/5

Several tools have overlapping purposes, such as multiple order creation tools (tronsave_create_order, tronsave_internal_order_create, tronsave_internal_create_extend_request) and multiple estimation tools (tronsave_estimate_buy_resource, tronsave_get_min_price, tronsave_internal_order_estimate). This would confuse an agent trying to select the correct tool.

Naming Consistency3/5

Tools follow a tronsave_verb_noun pattern with snake_case, but verbs are inconsistent (e.g., list vs get, create vs register) and the internal_ prefix creates two distinct naming styles. Some tools like tronsave_internal_order_book and tronsave_list_order_books are confusingly similar.

Tool Count2/5

29 tools is excessive for a server focused on a single market. Many tools duplicate functionality for internal vs signature authentication, bloating the surface. A more streamlined set (e.g., 10-15) would be more appropriate.

Completeness3/5

The tool set covers core operations like CRUD for orders, account info, and auto-settings. However, there are gaps: no explicit delete for auto-sell settings, and manual sell is the only sell option. Some internal tools appear redundant, but overall coverage is adequate.

Resources

Need Help?