Tronsave MCP Testnet

Internal Order Details

tronsave_internal_order_details

Read-onlyIdempotent

Fetch full details for one internal-account order by order ID. 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 monitoring fulfillment after tronsave_internal_order_create, or when the user asks for status on a specific order id. Read-only. FRESHNESS: order state changes within seconds as the market matches — re-read immediately before acting.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`orderId`	Yes	TronSave order ID (hex string), e.g. value returned in internal.order.create response data.orderId.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	TronSave order ID (hex string).
`price`	No	Unit price in SUN.
`status`	No	Order status.
`receiver`	No	TRON base58 receiver address.
`createdAt`	No	Order created time (Unix epoch ms or ISO-8601, endpoint-dependent).
`delegates`	No	Delegations fulfilling this order.
`orderType`	No	Order type (NORMAL \| FAST \| EXTEND).
`requester`	No	TRON base58 requester address.
`durationSec`	No	Delegated duration in seconds.
`payoutAmount`	No	Payout amount in SUN.
`remainAmount`	No	Remaining unfulfilled amount.
`resourceType`	No	Resource type.
`resourceAmount`	No	Resource amount of order.
`allowPartialFill`	No	Whether partial fill is allowed.
`fulfilledPercent`	No	0 = pending, 1-99 = partial, 100 = fully matched.

TDQS

A4.5/5.0

Behavior5/5

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

Discloses authentication requirements (needs mcp-session-id from tronsave_login, no API keys in arguments), differentiates session types, and adds freshness note about order state changes. Annotations already declare readOnlyHint, idempotentHint, openWorldHint; description adds beyond them.

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?

The description is concise and well-structured: purpose, authentication, usage context, read-only comment, freshness note. Every sentence adds value with no redundancy.

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 only one parameter, output schema present, and rich annotations, the description covers all essential aspects: purpose, authentication, usage, read-only nature, and data freshness. No gaps.

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 description coverage is 100% and adequately describes the orderId parameter. The tool description does not add extra semantics for the parameter; 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 it fetches full details for one internal-account order by order ID, using a specific verb and resource. It distinguishes from siblings by noting use cases like monitoring fulfillment after tronsave_internal_order_create or querying status by order ID.

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?

Explicitly tells when to use the tool (monitoring fulfillment, specific order status). Mentions read-only nature and the need for a logged-in session, but does not explicitly state when not to use. Still provides clear 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 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?