TronSave MCP Server

Get Minimum Unit Price

tronsave_get_min_price

Read-onlyIdempotent

Quote the minimum unit price for a buy. Use when only the floor price matters; for a full purchase quote use tronsave_estimate_buy_resource, for a grid across amounts and durations tronsave_get_price_table. Returns { minPrice } (SUN per resource unit; per day when durationSec >= 86400) from GraphQL market.estimateMinPrice for the given resourceType, buyAmount, and durationSec. Optional address scopes context when the API supports it. No login required. Read-only and idempotent. Pair with tronsave_estimate_buy_resource for full buy quotes and tronsave_list_order_books for depth buckets.

Input Schema

Name	Required	Description	Default
`address`	No	Optional TRON base58 address (`TronAddress`). When omitted, the server uses anonymous/global market context.
`buyAmount`	No	Resource amount to price (same units as order book / delegate amounts for that resource type). Default 100000 for ENERGY and 1000 for BANDWIDTH
`durationSec`	No	Delegation window in seconds; must match the duration you plan to use on a real order for comparable quotes. Default 15 minutes
`resourceType`	No	Market leg: `ENERGY` or `BANDWIDTH`. Default ENERGY	ENERGY

Output Schema

Name	Required	Description	Default
`minPrice`	No	Estimated minimum unit price in SUN for the given `resourceType`, `buyAmount`, and `durationSec`; align with `tronsave_estimate_buy_resource` and order `unitPrice` conventions (same as GraphQL `market.estimateMinPrice`).

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 28, 2026

addedInput schema / properties / address / pattern
```
Added value: +"^T[1-9A-HJ-NP-Za-km-z]{33}$"
```
changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

addedOutput schema / properties / minPrice / anyOf

Added value: +[
+  {
+    "description": "Estimated minimum unit price in SUN for the given `resourceType`, `buyAmount`, and `durationSec`; align with `tronsave_estimate_buy_resource` and order `unitPrice` conventions (same as GraphQL `market.estimateMinPrice`).",
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / minPrice / type
```
Removed value: -"number"
```
removedOutput schema / required
```
Removed value: -[
-  "minPrice"
-]
```

AddedMay 5, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the supplied annotations (readOnlyHint, idempotentHint, openWorldHint), the description discloses the auth requirement ('No login required'), the upstream source (`market.estimateMinPrice`), and the unit semantics of the returned value (SUN per resource unit, per day when durationSec >= 86400) — behavior that cannot be inferred from annotations. The only redundancy is restating 'Read-only and idempotent', which is harmless and non-contradictory.

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?

Three tight, front-loaded sentences leading with the core purpose and the routing decision. The closing sentence partially repeats the alternatives already named, which is mild redundancy rather than clutter.

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?

An output schema exists and annotations carry the safety profile, so the description needs only to explain selection, upstream source, and unit semantics — all of which it does. Nothing an agent needs to invoke the tool correctly is missing.

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 the baseline is 3; the description earns above that by tying `durationSec` to the returned unit (per-day when >= 86400) and by naming which inputs drive the quote (`resourceType`, `buyAmount`, `durationSec`) plus the scoping role of `address`. It does not add format or validation detail beyond that.

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?

States a specific verb and resource ('Quote the minimum unit price for a buy') and immediately distinguishes itself from `tronsave_estimate_buy_resource` (full quote) and `tronsave_get_price_table` (grid across amounts/durations). An agent can select it without opening a schema.

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?

Gives an explicit selection rule ('Use when only the floor price matters') plus named alternatives for the two adjacent use cases, and repeats the pairing guidance at the end. When-to-use and when-not-to-use are both covered.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?