Tronsave MCP Testnet

Internal Market Order Book

tronsave_internal_order_book

Read-onlyIdempotent

Return the current TronSave market depth/price tiers for ENERGY or BANDWIDTH via the api-key REST endpoint. 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 before tronsave_internal_order_create or tronsave_internal_order_estimate when the user needs live prices or liquidity. Read-only. FRESHNESS: live market depth can change roughly every 3 seconds (one TRON block) — re-read immediately before placing an order.

Input Schema

TableJSON Schema

Name	Required	Description
`address`	No	Optional TRON base58 address filter for the receiver.
`durationSec`	No	Delegation duration window in seconds for the quote.
`resourceType`	No	Resource type. Default ENERGY when omitted.
`minDelegateAmount`	No	Minimum resource amount per offer level to include (resource units, not SUN).

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	Order book entries sorted by price.
`fast`	No	FAST price tier (SUN).
`slow`	No	SLOW price tier (SUN).
`medium`	No	MEDIUM price tier (SUN).
`availableResource`	No	Available resource at the quoted tiers.

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds valuable context: auth mechanism (session-based, not API key via arguments), internal vs. api-key session behavior, and freshness behavior (changes every 3 seconds). No contradiction.

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 well-structured with multiple sentences, each adding essential info. It is front-loaded with the main purpose. While not extremely concise, it avoids fluff and every sentence earns its place. Could be slightly shorter, but still effective.

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 that an output schema exists (though not shown), the description covers authentication, usage context, parameter defaults, freshness, and read-only nature. It is complete for a read-only market book tool with good annotations.

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 context by noting that address and resourceType are optional with a default for resourceType, and explains minDelegateAmount meaning. This extra information justifies a 4.

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 it returns market depth/price tiers for ENERGY or BANDWIDTH, specifies the REST endpoint, and distinguishes itself from siblings like tronsave_internal_order_create by indicating usage before that tool. The verb (Return) and resource (market depth/price tiers) are specific.

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 requires a logged-in MCP session from tronsave_login, explains how to include the session ID, and advises to use before order_create or order_estimate when live prices are needed. Also notes the freshness caveat to re-read every 3 seconds.

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?