TronSave MCP Server

Estimate TRX Cost Before Order

tronsave_internal_order_estimate

Read-onlyIdempotent

Estimate the TRX cost and availability for a buy order before submitting it (api-key internal account). 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. Use when the user wants a quote or price check; feed the result into tronsave_internal_order_create. Read-only. FRESHNESS: unitPrice/estimateTrx are live and can change roughly every 3 seconds — re-estimate immediately before creating the order.

Input Schema

TableJSON Schema

Name	Required	Description
`options`	No	Optional flags that affect matching behavior for the estimate.
`receiver`	No	TRON base58 address that will receive the resource.
`requester`	No	TRON base58 requester; defaults to the API key account when omitted.
`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
`unitPrice`	No	Unit price in SUN.
`durationSec`	No	Delegated duration in seconds.
`estimateTrx`	No	Estimated TRX cost in SUN.
`availableResource`	No	Available resource amount.

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already mark readOnlyHint=true and idempotentHint=true. The description adds freshness info (live data changes every 3 seconds) and confirms read-only behavior, providing extra context 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, every sentence adds value: estimate purpose, login requirement, session type clarification, usage guidance, read-only note, and freshness detail. No waste.

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?

Given 7 parameters, nested objects, and an output schema, the description covers prerequisites, usage flow, behavioral nuances, and data freshness. Complete guidance for 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% with parameter descriptions. The description adds critical context: session ID inclusion (implicit parameter), and freshness constraints that inform parameter usage. This goes beyond 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 tool estimates TRX cost and availability for a buy order before submission. It uses a specific verb ('estimate') and resource ('TRX cost'), and distinguishes it from the sibling `tronsave_internal_order_create`.

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 states when to use ('when the user wants a quote or price check'), prerequisites (logged-in MCP session via `tronsave_login`), and how to feed results into the next tool. Explains session types.

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?