TronSave MCP Server

Order Book

tronsave_list_order_books

Read-onlyIdempotent

Read market depth buckets for ENERGY or BANDWIDTH. Public view; with an API key, tronsave_internal_order_book adds SLOW/MEDIUM/FAST price tiers. Returns price buckets { min, max, value } optionally scoped by viewer address, minimum delegate amount, and duration. No login required; read-only and idempotent. Use this to estimate market ranges before create/update decisions; pair with tronsave_estimate_buy_resource for quote-style buy estimation and tronsave_get_order for one concrete order.

Input Schema

Name	Required	Description
`address`	No	Optional viewer/requester wallet context.
`durationSec`	No	Optional delegation duration filter in seconds.
`resourceType`	Yes	Order-book side to query (`ENERGY` or `BANDWIDTH`).
`minDelegateAmount`	No	Optional minimum delegate amount floor for bucket filtering.

Output Schema

Name	Required	Description	Default
`orderBook`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 28, 2026

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

addedOutput schema / properties / orderBook / anyOf

Added value: +[
+  {
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "max": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "min": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "value": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / orderBook / items

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "max": {
-      "type": "number"
-    },
-    "min": {
-      "type": "number"
-    },
-    "value": {
-      "type": "number"
-    }
-  },
-  "required": [
-    "min",
-    "max",
-    "value"
-  ],
-  "type": "object"
-}

removedOutput schema / properties / orderBook / type
```
Removed value: -"array"
```
removedOutput schema / required
```
Removed value: -[
-  "orderBook"
-]
```

Changed4 schema fields changedApr 29, 2026

changedInput schema / properties / address / description

Previous value: -"Optional viewer/requester address."New value: +"Optional viewer/requester wallet context."

addedInput schema / properties / durationSec / description

Added value: +"Optional delegation duration filter in seconds."

addedInput schema / properties / minDelegateAmount / description

Added value: +"Optional minimum delegate amount floor for bucket filtering."

addedInput schema / properties / resourceType / description

Added value: +"Order-book side to query (`ENERGY` or `BANDWIDTH`)."

AddedApr 24, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered; the description adds real context on top: no login required, that an API key unlocks tiered data via another tool, and the exact return shape `{ min, max, value }`. It stops short of covering result limits, pagination or behavior on empty books, which keeps it below 5.

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?

Dense, front-loaded prose: purpose first, then tier/auth caveat, then return shape, then routing guidance. No filler sentences and no repetition of the tool title.

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 an output schema exists and annotations cover the safety profile, the description supplies everything else an agent needs: scope, auth tier differences, return structure, filtering semantics, and sibling routing. Nothing material is missing for a read-only market-depth query.

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, but the description frames the three optional params as a single coherent 'scoping' model (viewer address, minimum delegate amount, duration) that filters returned buckets, which is a meaningful clarification beyond the per-field schema text.

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?

Opens with a specific verb and resource: 'Read market depth buckets for ENERGY or BANDWIDTH'. It also explicitly distinguishes itself from the close sibling `tronsave_internal_order_book`, noting that the latter adds SLOW/MEDIUM/FAST tiers with an API key, so an agent can pick correctly without opening either schema.

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?

Gives an explicit use case ('estimate market ranges before create/update decisions') and routes two adjacent needs to named alternates: `tronsave_estimate_buy_resource` for quote-style buy estimation and `tronsave_get_order` for a single concrete order. Conditions for selecting the higher-tier sibling are also stated.

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?