TronSave MCP Server

Submit Delegation Extension

tronsave_internal_create_extend_request

Submit an extension request for existing delegated resources on TronSave, paid from the internal account. 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. Side effect: SPENDS internal TRX and creates an extension order; not idempotent. Use as STEP 2 after tronsave_internal_extend_delegates — pass its extendData rows unchanged. Returns { orderId } for the new extension order.

Input Schema

TableJSON Schema

Name	Required	Description
`receiver`	Yes	TRON base58 address of the account that receives the delegated resource.
`extendData`	Yes	Rows copied from `extendData` returned by `tronsave_internal_extend_delegates`.
`resourceType`	No	Resource type. Default ENERGY when omitted.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`orderId`	No	TronSave order ID (hex string) of the created/extension order.

TDQS

A4.9/5.0

Behavior5/5

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

The description discloses key behavioral traits beyond annotations: 'Side effect: SPENDS internal TRX and creates an extension order; not idempotent.' Annotations already indicate idempotentHint=false and readOnlyHint=false, but the description adds spending context and the nature of the side effect. No contradiction with annotations.

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?

The description is slightly lengthy but front-loaded with the core action. Each sentence provides unique value, covering purpose, prerequisites, side effects, and step usage. Could be slightly more concise, but no information is redundant.

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?

The description is complete given the output schema (returns { orderId }). It covers authentication, expected input (extendData from previous step), side effects, and typical workflow. No missing aspects for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds contextual meaning: extendData must be 'Rows copied from extendData returned by tronsave_internal_extend_delegates', receiver is a TRON base58 address, and resourceType defaults ENERGY. This aids correct parameter invocation.

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 title 'Submit Delegation Extension' and description clearly specify the action: submitting an extension request for delegated resources on TronSave. It distinguishes from sibling tools like tronsave_internal_extend_delegates (STEP 1) and tronsave_create_order by explicitly stating its role as STEP 2 and that it spends internal TRX.

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?

The description explicitly states usage guidance: 'Use as STEP 2 after tronsave_internal_extend_delegates — pass its extendData rows unchanged.' It also details authentication requirements (logged-in MCP session, include mcp-session-id) and clarifies that internal tools never accept API keys via arguments.

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?