TronSave MCP Server

User Permissions

tronsave_get_user_permissions

Read-onlyIdempotent

Read the enabled permission operations (autoSettings.permitOperations) for the authenticated user. Returns { permitOperations: string[] } — use it before mutating auto-sell or auto-buy rules to confirm the action is allowed for the wallet. Requires a wallet signature identity. Read-only and idempotent.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`permitOperations`	No	Permission rows enabled for this user; defaults to `[]` when nothing is configured.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 28, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

addedOutput schema / properties / permitOperations / anyOf

Added value: +[
+  {
+    "description": "Permission rows enabled for this user; defaults to `[]` when nothing is configured.",
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "id": {
+          "anyOf": [
+            {
+              "description": "Backend-assigned permission row id; null when not yet persisted.",
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Backend-assigned permission row id; null when not yet persisted."
+        },
+        "operations": {
+          "anyOf": [
+            {
+              "description": "Numeric operation codes enabled for this row; semantics defined by the backend.",
+              "items": {
+                "type": "number"
+              },
+              "type": "array"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Numeric operation codes enabled for this row; semantics defined by the backend."
+        },
+        "permissionName": {
+          "anyOf": [
+            {
+              "description": "Human-readable permission name; meant for display rather than equality checks.",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Human-readable permission name; meant for display rather than equality checks."
+        },
+        "type": {
+          "anyOf": [
+            {
+              "description": "Permission category as labelled by the backend (e.g. role/scope tag).",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Permission category as labelled by the backend (e.g. role/scope tag)."
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / permitOperations / default
```
Removed value: -[]
```

removedOutput schema / properties / permitOperations / items

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "id": {
-      "anyOf": [
-        {
-          "type": "number"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "Backend-assigned permission row id; null when not yet persisted."
-    },
-    "operations": {
-      "anyOf": [
-        {
-          "items": {
-            "type": "number"
-          },
-          "type": "array"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "Numeric operation codes enabled for this row; semantics defined by the backend."
-    },
-    "permissionName": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "Human-readable permission name; meant for display rather than equality checks."
-    },
-    "type": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "Permission category as labelled by the backend (e.g. role/scope tag)."
-    }
-  },
-  "type": "object"
-}

removedOutput schema / properties / permitOperations / type
```
Removed value: -"array"
```

removedOutput schema / required

Removed value: -[
-  "permitOperations"
-]

Changed5 schema fields changedMay 6, 2026
- addedOutput schema / properties / permitOperations / description
```
Added value: +"Permission rows enabled for this user; defaults to `[]` when nothing is configured."
```
- addedOutput schema / properties / permitOperations / items / properties / id / description
```
Added value: +"Backend-assigned permission row id; null when not yet persisted."
```
- addedOutput schema / properties / permitOperations / items / properties / operations / description
```
Added value: +"Numeric operation codes enabled for this row; semantics defined by the backend."
```
- addedOutput schema / properties / permitOperations / items / properties / permissionName / description
```
Added value: +"Human-readable permission name; meant for display rather than equality checks."
```
- addedOutput schema / properties / permitOperations / items / properties / type / description
```
Added value: +"Permission category as labelled by the backend (e.g. role/scope tag)."
```
AddedApr 24, 2026

TDQS

A4.4/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 the safety profile is covered; the description adds the non-obvious prerequisite that a wallet signature identity is required. The closing 'Read-only and idempotent' sentence merely restates the annotations, adding no new information.

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 short, front-loaded sentences: purpose first, return shape second, usage prerequisite third. The final clause about being read-only and idempotent duplicates the annotations and could be dropped without loss.

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?

An output schema exists, yet the description still names the key return field for quick scanning, and it covers the auth prerequisite and the pre-mutation check an agent needs before acting. Nothing required to invoke it 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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly does not invent parameter guidance that the empty schema contradicts.

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: reads the enabled permission operations (autoSettings.permitOperations) for the authenticated user. It is clearly distinct from siblings like tronsave_get_user_auto_setting and tronsave_get_user_info by naming the exact setting field it returns.

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 call it before mutating auto-sell or auto-buy rules to confirm the action is allowed, which routes the agent away from blind mutation via tronsave_update_auto_sell_setting / tronsave_update_auto_buy_setting. It does not state any when-not-to-use condition, but the scope is narrow enough that this is a minor gap.

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?