Tronsave MCP Testnet

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

Behavior5/5

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

Adds significant context beyond annotations: requires logged-in session, explains session types, freshness warning, and instruction to pass extendData unchanged. 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?

Front-loaded main purpose, then provides necessary details. A bit lengthy but each sentence adds value.

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

Completeness3/5

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

Covers session, workflow, and freshness. Does not differentiate from sibling tronsave_list_extendable_delegates or explain return details beyond what output schema likely provides.

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 coverage is 100%, so baseline is 3. Description does not add extra meaning to parameters beyond the schema's descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it returns extendable delegations and extendData payload, and positions it as STEP 1 in a workflow. However, it does not distinguish from sibling tool 'tronsave_list_extendable_delegates' which may serve a similar purpose.

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 says when to use (before tronsave_internal_create_extend_request) and that it's read-only. Does not provide when-not-to-use or alternatives, 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 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?