TronSave MCP Server

List Extendable Delegations

tronsave_internal_extend_delegates

Read-onlyIdempotent

Return extendable delegations for a receiver plus an extendData payload for the extension flow. 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 as STEP 1 before tronsave_internal_create_extend_request when the user wants to extend existing delegation time. Read-only; does not submit anything. FRESHNESS: pricing/availability change within seconds — run immediately before extending and pass the returned extendData unchanged.

Input Schema

TableJSON Schema

Name	Required	Description
`extendTo`	Yes	Target end time as Unix epoch milliseconds (UTC) for the extended delegation.
`receiver`	Yes	TRON base58 address of the account that receives the delegated resource.
`requester`	No	TRON base58 requester; defaults to the API key account when omitted.
`resourceType`	No	Resource type. Default ENERGY when omitted.
`maxPriceAccepted`	No	Maximum unit price in SUN you are willing to pay for the extension.

Output Schema

TableJSON Schema

Name	Required	Description
`extendData`	No	Delegations to extend; pass unchanged into internal_create_extend_request `extendData`.
`yourBalance`	No	Current account balance in SUN.
`isAbleToExtend`	No	Whether balance is sufficient to extend.
`extendOrderBook`	No	Order book for extend.
`totalEstimateTrx`	No	Total estimated TRX cost in SUN.
`totalDelegateAmount`	No	Total delegated resource amount.
`totalAvailableExtendAmount`	No	Total available amount to extend.

TDQS

A4.3/5.0

Behavior4/5

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

While annotations already declare readOnly, openWorld, and idempotent hints, the description adds essential context about session requirements, freshness sensitivity, and the extendData return payload.

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?

Well-structured with purpose upfront, but slightly verbose with repeated session and internal tool notes. Could be tightened without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Provides flow context, return data description, and freshness warning. Output schema exists (not shown) so return behavior is covered. Lacks only minor details like error conditions.

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 has 100% coverage with good descriptions; the description does not add significant meaning beyond the schema, so 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?

Clearly states it returns extendable delegations and an extendData payload for the extension flow, distinguishing it from sibling tools like tronsave_internal_create_extend_request.

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 identifies this as STEP 1 before tronsave_internal_create_extend_request, provides session setup requirements, and states it is read-only and does not submit.

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?