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 the updated order payload after sell. Side effect: broadcasts a market/delegation transaction and may consume balances/resources; not idempotent — each call re-executes. Backend requires a signature session and mcp-session-id; the MCP gate is public to allow anonymous read-fallthrough, but the GraphQL helper rejects api-key-only sessions. Use only when explicit manual sell is intended; call tronsave_get_order first to verify order state before signing.

Input Schema

TableJSON 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

TableJSON Schema

Name	Required	Description
`code`	Yes	GraphQL mutation status code (HTTP-like; `0`/`200` indicates success). Always pair with `success` for 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`.
`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.

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

Behavior5/5

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

Beyond annotations (destructiveHint=true, idempotentHint=false), the description adds key behaviors: 'broadcasts a market/delegation transaction', 'may consume balances/resources', and explicitly states 'not idempotent — each call re-executes'. No contradiction with annotations. This provides actionable insight.

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?

Three sentences with front-loaded purpose. Slightly verbose on auth details, but each sentence earns its place. Structure is logical: purpose, side effects/auth, usage guidance.

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?

Given complexity (nested params, output schema exists), the description covers purpose, usage, side effects, auth, and relation to sibling tools. No missing critical information for agent decision-making.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value: for orderId it notes eligibility criteria, for signedTx it warns against fabrication and explains origin, and for paymentAddress it clarifies optional use. Meaningfully supplements 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 specifies the action ('manually execute seller-side fulfillment'), the resource ('existing order'), and the required input ('wallet signedTx'). It distinguishes from siblings by stating 'Use only when explicit manual sell is intended' and recommends calling tronsave_get_order first, making the purpose clear.

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?

Provides explicit guidance on when to use ('explicit manual sell intended') and prerequisites ('call tronsave_get_order first to verify order state before signing'). It also details authentication requirements (signature session, mcp-session-id) and warns about API-key-only sessions. Does not exhaustively list when not to use alternatives, but context is strong.

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?