TronSave MCP Server

Sell Order Manual

tronsave_sell_order_manual

Destructive

Manually execute seller-side fulfillment of an existing order with a wallet signedTx. Returns { success, message, code, delegatedId }. Side effect: broadcasts a market/delegation transaction and may consume balances/resources; not idempotent — each call re-executes. Requires a wallet signature identity. Use only when explicit manual sell is intended; call tronsave_get_order first to verify order state before signing.

Input Schema

Name	Required	Description
`orderId`	Yes	Target order id (`MObjectId`) to manually fulfill. Should be an order eligible for seller-side manual execution.
`signedTx`	Yes	Required wallet-signed transaction payload (TronWeb shape: `{ txID, raw_data, raw_data_hex, signature[] }`). Must come from client-side signing; never fabricate.
`paymentAddress`	No	Optional payout/payment address override when settlement flow requires it.

Output Schema

Name	Required	Description
`code`	No	GraphQL mutation status code (HTTP-like; `0`/`200` indicates success). Always pair with `success` for routing.
`message`	No	Human-readable status text. Populated even on success; localized error messages may appear here on failure.
`success`	No	Whether the mutation succeeded at the backend level. Always check this before reading `data`.
`delegatedId`	No	On-chain delegate id created by the manual sell when the underlying transaction is confirmed; null until confirmation lands.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 28, 2026

addedInput schema / properties / paymentAddress / pattern
```
Added value: +"^T[1-9A-HJ-NP-Za-km-z]{33}$"
```
changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

addedOutput schema / properties / code / anyOf

Added value: +[
+  {
+    "description": "GraphQL mutation status code (HTTP-like; `0`/`200` indicates success). Always pair with `success` for routing.",
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / code / maximum
```
Removed value: -9007199254740991
```
removedOutput schema / properties / code / minimum
```
Removed value: --9007199254740991
```
removedOutput schema / properties / code / type
```
Removed value: -"integer"
```

changedOutput schema / properties / delegatedId / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "On-chain delegate id created by the manual sell when the underlying transaction is confirmed; null until confirmation lands.",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / message / anyOf

Added value: +[
+  {
+    "description": "Human-readable status text. Populated even on success; localized error messages may appear here on failure.",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / message / type
```
Removed value: -"string"
```

addedOutput schema / properties / success / anyOf

Added value: +[
+  {
+    "description": "Whether the mutation succeeded at the backend level. Always check this before reading `data`.",
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / success / type
```
Removed value: -"boolean"
```

removedOutput schema / required

Removed value: -[
-  "code",
-  "success",
-  "message"
-]

Changed9 schema fields changedMay 6, 2026

addedInput schema / properties / signedTx / additionalProperties
```
Added value: +{}
```

changedInput schema / properties / signedTx / description

Previous value: -"Required wallet-signed transaction payload (GraphQL JSON scalar). Must come from client-side signing; never fabricate."New value: +"Required wallet-signed transaction payload (TronWeb shape: `{ txID, raw_data, raw_data_hex, signature[] }`). Must come from client-side signing; never fabricate."

addedInput schema / properties / signedTx / properties

Added value: +{
+  "raw_data": {
+    "additionalProperties": {},
+    "description": "Raw transaction body produced by TronWeb (`raw_data`).",
+    "properties": {
+      "contract": {
+        "description": "At least one TRON contract entry; shape varies by contract type.",
+        "items": {},
+        "minItems": 1,
+        "type": "array"
+      },
+      "expiration": {
+        "description": "Tx expiration (Unix epoch ms).",
+        "exclusiveMinimum": 0,
+        "maximum": 9007199254740991,
+        "type": "integer"
+      },
+      "ref_block_bytes": {
+        "description": "Reference block bytes (hex).",
+        "type": "string"
+      },
+      "ref_block_hash": {
+        "description": "Reference block hash (hex).",
+        "type": "string"
+      },
+      "timestamp": {
+        "description": "Tx timestamp (Unix epoch ms).",
+        "exclusiveMinimum": 0,
+        "maximum": 9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "contract",
+      "ref_block_bytes",
+      "ref_block_hash",
+      "expiration",
+      "timestamp"
+    ],
+    "type": "object"
+  },
+  "raw_data_hex": {
+    "description": "Hex-encoded `raw_data` body.",
+    "pattern": "^[0-9a-fA-F]+$",
+    "type": "string"
+  },
+  "signature": {
+    "description": "Wallet signatures over `raw_data_hex`; usually a single hex string (130 chars for 65-byte secp256k1).",
+    "items": {
+      "minLength": 1,
+      "pattern": "^[0-9a-fA-F]+$",
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  "txID": {
+    "description": "Transaction hash (64 hex chars, lowercase, no `0x` prefix).",
+    "maxLength": 64,
+    "minLength": 64,
+    "pattern": "^[0-9a-fA-F]+$",
+    "type": "string"
+  },
+  "visible": {
+    "description": "Whether addresses inside `raw_data.contract` are base58 (`true`) vs hex (`false`).",
+    "type": "boolean"
+  }
+}

addedInput schema / properties / signedTx / required

Added value: +[
+  "txID",
+  "raw_data",
+  "raw_data_hex",
+  "signature"
+]

addedInput schema / properties / signedTx / type
```
Added value: +"object"
```

addedOutput schema / properties / code / description

Added value: +"GraphQL mutation status code (HTTP-like; `0`/`200` indicates success). Always pair with `success` for routing."

addedOutput schema / properties / delegatedId / description

Added value: +"On-chain delegate id created by the manual sell when the underlying transaction is confirmed; null until confirmation lands."

addedOutput schema / properties / message / description

Added value: +"Human-readable status text. Populated even on success; localized error messages may appear here on failure."

addedOutput schema / properties / success / description

Added value: +"Whether the mutation succeeded at the backend level. Always check this before reading `data`."

Changed3 schema fields changedApr 29, 2026

changedInput schema / properties / orderId / description

Previous value: -"Order id (`MObjectId`)."New value: +"Target order id (`MObjectId`) to manually fulfill. Should be an order eligible for seller-side manual execution."

changedInput schema / properties / paymentAddress / description

Previous value: -"Optional payout/payment address."New value: +"Optional payout/payment address override when settlement flow requires it."

changedInput schema / properties / signedTx / description

Previous value: -"Signed transaction payload (GraphQL JSON scalar)."New value: +"Required wallet-signed transaction payload (GraphQL JSON scalar). Must come from client-side signing; never fabricate."

AddedApr 24, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare destructive, non-idempotent, and open-world behavior, and the description adds concrete context: it broadcasts a market/delegation transaction, may consume balances/resources, and re-executes on each call. It also states the wallet signature identity requirement and return shape, with no contradiction to annotations.

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 description is a single dense paragraph, front-loaded with the action and followed by side effects, prerequisites, and return shape. Every sentence adds useful information with no wasted text.

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?

For a destructive transaction tool with a nested payload and an output schema, the description supplies the critical behavioral context: side effects, non-idempotency, signature requirement, and a pre-check with tronsave_get_order. The output schema covers return-value details, so nothing essential is missing for correct invocation.

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%, and the schema fully documents orderId, the nested signedTx payload, and paymentAddress. The description only reiterates wallet signedTx and order-state verification, adding no syntax or format details beyond the 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?

States a specific verb and resource: manually execute seller-side fulfillment of an existing order using a wallet signedTx. The word 'manual' and the 'existing order' scope distinguish it from sibling order creation, cancellation, update, and automated-sell tools.

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 to use it only when an explicit manual sell is intended and to call tronsave_get_order first to verify order state before signing. This gives a clear condition and prerequisite, though it does not name a specific alternative for automated selling.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?