Tronsave MCP Testnet

Create Energy or Bandwidth Order (Internal)

tronsave_internal_order_create

Place a new buy order for ENERGY or BANDWIDTH on TronSave, paid from the internal account balance. Requires a logged-in MCP session created by the tronsave_login tool: include mcp-session-id: <sessionId> returned by tronsave_login on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. Side effect: SPENDS internal TRX balance and creates a live order; not idempotent — each call places a new order. This is the api-key/internal path; for the signature-session market path use tronsave_create_order. Always derive unitPrice from the latest tronsave_internal_order_estimate (re-estimate immediately before submitting — quotes older than a few seconds may be stale and revert). Returns { orderId }.

Input Schema

TableJSON Schema

Name	Required	Description
`options`	No	Optional execution guards and fill behavior.
`sponsor`	No	Optional sponsor or referral code.
`receiver`	Yes	TRON base58 address that will receive the resource.
`unitPrice`	No	Pricing: FAST \| MEDIUM \| SLOW strategy, or exact unit price in SUN per resource unit. Default MEDIUM when omitted.
`durationSec`	No	Delegation duration in seconds. Default 259200 (3 days) when omitted.
`resourceType`	No	Resource type. Default ENERGY when omitted.
`resourceAmount`	Yes	Amount of resource to purchase (resource units).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`orderId`	No	TronSave order ID (hex string) of the created/extension order.

TDQS

A4.8/5.0

Behavior5/5

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

Discloses side effect: 'SPENDS internal TRX balance and creates a live order; not idempotent — each call places a new order.' This adds detail beyond the annotations (idempotentHint false) and explains the impact and non-idempotency clearly.

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 a single paragraph that front-loads purpose, then prerequisites, side effects, distinctions, and guidance. Every sentence adds value, though it could be slightly more structured (e.g., bullet points). Length is appropriate for the complexity.

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?

Covers all required context: session requirement, side effects, non-idempotency, sibling tool distinction, pricing guidance from estimate, and return value ({ orderId }). Output schema exists but description still mentions the return shape, which is helpful.

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%, so baseline is 3. The description adds meaning by explaining how to use unitPrice (derive from estimate), that options control fill behavior, and that durationSec defaults to 3 days. This exceeds mere repetition of schema.

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 action: 'Place a new buy order for ENERGY or BANDWIDTH on TronSave, paid from the internal account balance.' It distinguishes from sibling tool tronsave_create_order by specifying this is the api-key/internal path versus the signature-session market path.

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?

Explicitly requires a logged-in MCP session from tronsave_login and provides the mcp-session-id header. It contrasts with the signature-session alternative (tronsave_create_order). Also advises to derive unitPrice from the latest tronsave_internal_order_estimate and warns about stale quotes.

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?