TronSave MCP Server

Update Order

tronsave_update_order

Update an open order by orderId with partial fields (receiver, newPrice). Returns { success, message, code }. Side effect: overwrites live order parameters; not idempotent — each call with a different newPrice produces a new state. Requires a wallet signature identity (the order's owner). Prefer this over cancel+recreate when only price/receiver should change. Verify state with tronsave_get_order first; fails for already-fulfilled, already-cancelled, or non-editable orders.

Input Schema

Name	Required	Description
`orderId`	Yes	Target order id (`MObjectId`) to update. Order must still be open and editable.
`newPrice`	No	Optional replacement unit price in SUN per resource unit.
`receiver`	No	Optional replacement receiver TRON address.

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`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedOct 28, 2026

changedInput schema / properties / newPrice / description

Previous value: -"Optional replacement unit price in SUN."New value: +"Optional replacement unit price in SUN per resource unit."

addedInput schema / properties / newPrice / exclusiveMinimum
```
Added value: +0
```
addedInput schema / properties / receiver / 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"
```

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"
-]

Changed3 schema fields changedMay 6, 2026

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 / 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 / newPrice / description

Previous value: -"Optional new unit price."New value: +"Optional replacement unit price in SUN."

changedInput schema / properties / orderId / description

Previous value: -"Order id (`MObjectId`) to update."New value: +"Target order id (`MObjectId`) to update. Order must still be open and editable."

changedInput schema / properties / receiver / description

Previous value: -"Optional new receiver address."New value: +"Optional replacement receiver TRON address."

AddedApr 24, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly=false, idempotent=false, destructive=false, openWorld=true, but the description adds context annotations cannot: it overwrites live order parameters, each distinct `newPrice` produces a new state, and a wallet-signature identity (owner) is required. It also states the return shape and the preconditions for failure, which goes well beyond the annotation bar.

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?

Four dense sentences, front-loaded with the action, then the return shape, then side effects, then alternatives and preconditions. Every sentence adds a decision-relevant fact; there is no filler or repetition of the schema.

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?

Although an output schema exists (so return values need not be described), the description still summarizes the return shape and covers the mutation, identity requirement, non-idempotency, failure states, and the alternative workflow. Nothing an agent needs to invoke this correctly is missing.

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 the baseline is 3, but the description adds semantic constraints the schema only implies: the update is partial, the caller must be the order's owner (signature identity), and `orderId` must refer to an editable order. It does not add syntax or units beyond what the schema already documents for `newPrice` (SUN) and `receiver` (TRON address pattern).

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 ('Update an open order by `orderId` with partial fields') and names the exact mutable fields, so an agent can tell it apart from `tronsave_cancel_order` or `tronsave_create_order` without reading the schema. The scope restriction ('open order') is front-loaded.

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 routes the agent: 'Prefer this over cancel+recreate when only price/receiver should change' names the alternative and the selecting condition. It also prescribes a prerequisite ('Verify state with `tronsave_get_order` first') and enumerates failure cases (fulfilled, cancelled, non-editable).

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?