Tronsave MCP Testnet

Estimate Buy Resource

tronsave_estimate_buy_resource

Read-onlyIdempotent

Quote price and availability for buying ENERGY or BANDWIDTH for a receiver address before placing an order. Returns estimated unitPrice (SUN per resource unit), paymentAmount, and availability fields used to populate tronsave_create_order inputs (orderUnitPrice, paymentPaymentAmount). Read-only and safe to call repeatedly; no session is required, but backend rate limits apply. FRESHNESS: this is live market data — unitPrice/availability can change roughly every 3 seconds (one TRON block). Re-run this estimate immediately before tronsave_create_order and never reuse a quote more than a few seconds old. For order-book depth use tronsave_list_order_books; for the minimum unit price only use tronsave_get_min_price.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`receiver`	No	receiver address.
`unitPrice`	No	Unit price in SUN.
`durationSec`	No	Duration of the order in seconds. Default 15 minutes
`resourceType`	No	Resource type to buy. Default ENERGY	ENERGY
`allowPartialFill`	No	Allow partial fill of the order.
`buyResourceAmount`	No	Amount of resource to buy. Default 100000 for ENERGY and 1000 for BANDWIDTH
`minResourceDelegateRequiredAmount`	No	Minimum amount of resource to delegate.

Output Schema

TableJSON Schema

Name	Required	Description
`unitPrice`	Yes	Unit price in SUN
`durationSec`	Yes	Delegated duration in seconds
`estimateTrx`	Yes	Estimated TRX cost in SUN
`availableResource`	Yes	Available resource amount
`systemDepositAddress`	Yes	System deposit address for onchain payment

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint. Description adds no session required, backend rate limits, and data freshness (changes every TRON block ~3 seconds), providing value beyond annotations.

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?

Length is appropriate; front-loaded with purpose, then guidelines, then freshness warning, then sibling differentiation. Every sentence serves a purpose, though slightly verbose.

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 7 optional parameters, rich annotations, and output schema, description covers the tool's role, freshness, sibling alternatives, and key output fields. Does not detail output schema but that is acceptable since schema exists.

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% with each parameter described. Description adds context about receiver address and output fields (unitPrice, paymentAmount, availability) but does not deepen parameter semantics beyond schema. Baseline 3.

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?

Description clearly states it quotes price and availability for buying ENERGY or BANDWIDTH for a receiver address. Distinguishes from siblings like tronsave_create_order (uses quotes), tronsave_list_order_books (order-book depth), and tronsave_get_min_price (minimum price only).

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 advises to re-run immediately before tronsave_create_order, not to reuse a quote more than a few seconds old, and contrasts with sibling tools. States it is read-only and safe for repeated calls.

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?