TronSave MCP Server

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

Behavior5/5

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

Annotations already provide readOnlyHint, openWorldHint, and idempotentHint. The description adds valuable behavioral context: requirements for session ID, explanation of session vs API key usage, and a freshness warning about rapid state changes. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with three sentences plus a freshness note, front-loading the primary purpose. Every sentence adds value.

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 the presence of an output schema, the description covers all needed aspects: purpose, usage context, prerequisites, and freshness. It is fully adequate for a read-only fetch tool.

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 an example hint about the source of the orderId, improving usability without repeating schema details.

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 'Fetch full details for one internal-account order by order ID.' It specifies the verb, resource, and scope, distinguishing it from sibling tools like tronsave_get_order and tronsave_internal_order_book.

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 provides explicit usage scenarios: 'Use when monitoring fulfillment after tronsave_internal_order_create, or when the user asks for status on a specific order id.' It also mentions the prerequisite of a logged-in MCP session. It does not explicitly state when not to use, but the 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 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?