TronSave MCP Server

Update Auto Sell Setting

tronsave_update_auto_sell_setting

Update the existing auto-sell configuration with partial fields. Returns the updated autoSettings payload. Side effect: overwrites stored automation settings for the current user; not idempotent across different field sets. Requires a signature session and mcp-session-id. Use for INCREMENTAL changes after registration; read the baseline via tronsave_get_user_auto_setting to avoid accidental resets, and use tronsave_register_auto_sell only for first-time setup. Fails for invalid field combinations, unauthorized sessions, or policy constraints.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`poolSetting`	No
`addOnFeature`	No
`paymentConfig`	No

Output Schema

TableJSON Schema

Name	Required	Description
`code`	Yes	GraphQL mutation status code (HTTP-like; `0`/`200` indicates success). Always pair with `success` for routing.
`data`	Yes	Opaque server-defined payload (tx id, setting id, or status text). Treat as identifier-or-message; rely on `message` for human routing.
`message`	Yes	Human-readable status text. Populated even on success; localized error messages may appear here on failure.
`success`	Yes	Whether the mutation succeeded at the backend level. Always check this before reading `data`.

TDQS

A4.6/5.0

Behavior5/5

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

Description adds important side-effect details ('overwrites stored automation settings for the current user; not idempotent across different field sets') that go beyond annotations (readOnlyHint false, destructiveHint false, idempotentHint false). 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?

Three sentences, each dense with information. Front-loaded with purpose, followed by side effects and usage guidance. No redundant words.

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?

Covers purpose, usage, side effects, prerequisites, alternatives, failure conditions, and notes output schema existence. Complete for a complex tool with nested parameters.

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

Parameters2/5

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

Despite 0% schema coverage, the description provides minimal guidance on parameters. It mentions 'partial fields' but does not explain the complex nested structure or the role of each property. The schema itself has descriptions, but the description should add value beyond schema.

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 uses a specific verb ('Update') and resource ('auto-sell configuration') and distinguishes from sibling tools like 'tronsave_register_auto_sell' and 'tronsave_get_user_auto_setting'.

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 states when to use ('incremental changes after registration'), when not to use ('use tronsave_register_auto_sell only for first-time setup'), and prerequisites ('requires a signature session and mcp-session-id'). Also lists failure conditions.

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?