Tronsave MCP Testnet

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

Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint. The description adds valuable operational context: session-based auth (no API keys), freshness note (data changes every 3 seconds, re-estimate before create). No contradictions.

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 of 5 sentences, front-loaded with purpose and prerequisites. It is relatively concise but could be more structured (e.g., bullet points). No wasted sentences.

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 (1 required), nested objects, output schema exists, the description covers purpose, prerequisites, usage, authentication, freshness, and links to next tool. It is complete for the complexity level.

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%, so the description does not need to add much. It does not elaborate on parameter meaning beyond what the schema provides. The freshness note refers to output fields, not inputs. Baseline 3 is appropriate.

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, with a specific verb and resource. It distinguishes itself from siblings like tronsave_internal_order_create by positioning as a pre-order quote step.

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 explicitly says 'Use when the user wants a quote or price check' and directs to feed results into tronsave_internal_order_create. Prerequisites (logged-in session, session ID header) are provided. Lacks explicit when-not-to-use, but context is clear.

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?