TronSave MCP Server

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

Behavior5/5

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

Annotations already indicate read-only, open-world, idempotent. Description adds critical freshness behavior: data changes every ~3 seconds (TRON block) and advises re-reading before orders. Also explains internal tool authentication flow beyond annotations. 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?

Description is a single coherent paragraph, front-loads core purpose. Every sentence adds value, but could be slightly restructured for readability. No wasted words, but not extremely concise.

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 (not shown but indicated), the description need not explain return values. It covers purpose, usage prerequisites, freshness constraints, and tool relationships. Fully sufficient for an agent to use this tool correctly.

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?

Input schema has 100% description coverage for all 4 parameters. The description only reiterates the default for resourceType ('ENERGY when omitted') which is already in the schema. No additional meaning beyond schema, so baseline score of 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?

Clearly states the tool returns market depth/price tiers for ENERGY or BANDWIDTH. Distinguishes from siblings by positioning it as a prerequisite for tronsave_internal_order_create and tronsave_internal_order_estimate.

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 says when to use (before creating/estimating orders needing live prices) and provides detailed prerequisites: requires logged-in MCP session from tronsave_login, describes session types and authentication method. Effectively guides the agent on proper invocation context.

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?