TronSave MCP Server

Official

by tronsave

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

List Extendable Delegations

tronsave_internal_extend_delegates

Read-onlyIdempotent

Retrieve extendable delegations for a receiver and return the extendData payload needed to extend existing delegation time, as a read-only first step before creating an extension request.

Instructions

Return extendable delegations for a receiver plus an extendData payload for the extension flow. Requires an internal API key: tronsave_login (api-key mode, or signature mode for a wallet with an internal account) or an Authorization: ApiKey <key> client header. Never pass API keys as tool arguments; the server forwards the key from the session/header to TronSave. 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

Name	Required	Description
`extendTo`	Yes	Target end time as Unix epoch SECONDS (UTC) for the extended delegation, e.g. now + 86400 for one more day. Milliseconds are rejected by TronSave (INVALID_EXTEND_TIME).
`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

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.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0Nov 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond annotations, it discloses the authentication requirements, warns never to pass API keys as tool arguments, explains server-side key forwarding, and clarifies that the operation is read-only and does not submit anything. It also adds the important freshness constraint that pricing/availability changes within seconds and that `extendData` must be passed unchanged.

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 purpose is front-loaded in the first sentence, followed by auth, workflow placement, read-only status, and freshness guidance. Every sentence adds operational value with no redundant restatement.

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?

With an output schema present, the description does not need to enumerate return fields, and it already covers the critical context: authentication, workflow sequencing, read-only behavior, and freshness. Given the rich schema and annotations, this is complete for an agent to call it 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?

Schema description coverage is 100%, so the schema already documents all five parameters thoroughly. The description reinforces the receiver and extendData concepts but does not add meaningful syntax or constraints beyond what the schema provides, so the baseline 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?

It states a specific verb and resource: return extendable delegations plus an `extendData` payload for the extension flow. The internal API key requirement and the step-1 relationship to `tronsave_internal_create_extend_request` distinguish it from the general list siblings.

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?

It explicitly says to use this as STEP 1 before `tronsave_internal_create_extend_request` when extending existing delegation time, and adds a freshness rule to run immediately before extending. The read-only clause also makes clear it is not the submission step.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server