TronSave MCP Server

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.8/5.0

Behavior5/5

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint. The description adds beyond: 'no session is required', 'backend rate limits apply', and data freshness of approximately 3 seconds. No contradictions with 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?

At about 100 words, it is concise. All sentences add value: purpose, freshness warning, sibling differentiation. Slight redundancy with annotations is acceptable. Front-loaded with main action.

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?

With 7 parameters (no required), many siblings, and an output schema, the description covers purpose, usage context, data freshness, rate limits, and parameter-output linkages. No gaps remain for an agent to understand correct invocation.

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 linking output fields to `tronsave_create_order` inputs and providing default values for `durationSec`, `resourceType`, and `buyResourceAmount`. This contextualizes parameters beyond the schema alone.

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 verb 'Quote', the resource 'ENERGY or BANDWIDTH', and the receiver address. It distinguishes the tool from siblings by naming `tronsave_list_order_books` and `tronsave_get_min_price` as alternatives for different needs.

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?

Explicit usage guidance: use before `tronsave_create_order`, do not reuse estimates older than a few seconds, re-run immediately before ordering. Alternatives are named for depth and minimum price queries.

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

All TronSave MCP Server 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

A4.4/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, with some overlap between signature-based and internal API-based variants (e.g., create_order vs internal_order_create). Descriptions are thorough and help disambiguate. The minor overlap is justified by different authentication methods.

Naming Consistency5/5

Tool names follow a consistent 'tronsave_verb_noun' pattern with clear segmentation (e.g., get/list for retrieval, create/update/cancel for mutations). Internal tools use a consistent 'internal_' prefix. No mixing of conventions.

Tool Count4/5

29 tools is on the higher end but appropriate for a DeFi platform covering multiple resource types, order management, auto-settings, internal accounts, extensions, and authentication. A few tools could be merged (e.g., estimate variants) but overall scope justifies the count.

Completeness3/5

Major operations (CRUD for orders, auto-sell settings, internal account) are covered. Notable gaps include missing create/update tools for auto-buy rules (only delete exists) and limited history for signature-based orders (only internal order history available).

Resources

Need Help?