TronSave MCP Server

Login Session

tronsave_login

Log in to TronSave for the rest of this MCP connection. Provide EXACTLY ONE of: signature = <signature>_<timestamp> produced by the user's wallet over the message from tronsave_get_sign_message (unlocks wallet tools; also loads the wallet's internal API key if it has one), or apiKey = raw TronSave internal API key (unlocks internal-account tools and paymentMethod=internal). The login is bound to the current mcp-session-id automatically — do not pass session ids in later tool arguments. Returns { sessionId, authMode, walletAddress?, hasInternalApiKey, expiresAt, unlocked }. Signed timestamps older than the server limit (default 24h) are rejected with SIGNATURE_EXPIRED. Never ask the user for private keys or seed phrases.

Input Schema

Name	Required	Description	Default
`apiKey`	No	Raw API key for internal-tools login. Provide EXACTLY ONE of `apiKey` or `signature`.
`signature`	No	Signature token in `signature_timestamp` format (timestamp is the signed message). Provide EXACTLY ONE of `apiKey` or `signature`.

Output Schema

Name	Required	Description
`authMode`	No	Which credential type the session holds.
`unlocked`	No	Human-readable summary of the tool groups now available.
`warnings`	No	Non-fatal issues (e.g. internal API key could not be loaded).
`expiresAt`	No	Session expiry (ISO-8601).
`sessionId`	No	The MCP session (`mcp-session-id`) the login is bound to. MCP clients resend it automatically; never pass it as a tool argument.
`walletAddress`	No	Wallet recovered from the signature (signature mode only).
`hasInternalApiKey`	No	Whether internal-account tools and `paymentMethod=internal` are usable in this session.

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedOct 28, 2026

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

addedOutput schema / properties / authMode

Added value: +{
+  "anyOf": [
+    {
+      "description": "Which credential type the session holds.",
+      "enum": [
+        "signature",
+        "api-key"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Which credential type the session holds."
+}

addedOutput schema / properties / expiresAt / anyOf

Added value: +[
+  {
+    "description": "Session expiry (ISO-8601).",
+    "format": "date-time",
+    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / expiresAt / description
```
Added value: +"Session expiry (ISO-8601)."
```
removedOutput schema / properties / expiresAt / format
```
Removed value: -"date-time"
```

removedOutput schema / properties / expiresAt / pattern

Removed value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"

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

addedOutput schema / properties / hasInternalApiKey

Added value: +{
+  "anyOf": [
+    {
+      "description": "Whether internal-account tools and `paymentMethod=internal` are usable in this session.",
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Whether internal-account tools and `paymentMethod=internal` are usable in this session."
+}

addedOutput schema / properties / sessionId / anyOf

Added value: +[
+  {
+    "description": "The MCP session (`mcp-session-id`) the login is bound to. MCP clients resend it automatically; never pass it as a tool argument.",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / sessionId / description

Previous value: -"Session id to pass as mcp-session-id in subsequent calls."New value: +"The MCP session (`mcp-session-id`) the login is bound to. MCP clients resend it automatically; never pass it as a tool argument."

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

addedOutput schema / properties / unlocked

Added value: +{
+  "anyOf": [
+    {
+      "description": "Human-readable summary of the tool groups now available.",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Human-readable summary of the tool groups now available."
+}

addedOutput schema / properties / walletAddress / anyOf

Added value: +[
+  {
+    "description": "Wallet recovered from the signature (signature mode only).",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / walletAddress / description

Added value: +"Wallet recovered from the signature (signature mode only)."

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

addedOutput schema / properties / warnings

Added value: +{
+  "anyOf": [
+    {
+      "description": "Non-fatal issues (e.g. internal API key could not be loaded).",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Non-fatal issues (e.g. internal API key could not be loaded)."
+}

removedOutput schema / required

Removed value: -[
-  "sessionId",
-  "expiresAt"
-]

Changed1 schema field changedMay 6, 2026

changedInput schema / properties / signature / description

Previous value: -"Signature token in `signature_timestamp` format (timestamp is the signed message nonce). Provide EXACTLY ONE of `apiKey` or `signature`."New value: +"Signature token in `signature_timestamp` format (timestamp is the signed message). Provide EXACTLY ONE of `apiKey` or `signature`."

Changed3 schema fields changedMay 5, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / properties / apiKey

Added value: +{
+  "description": "Raw API key for internal-tools login. Provide EXACTLY ONE of `apiKey` or `signature`.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / signature

Added value: +{
+  "description": "Signature token in `signature_timestamp` format (timestamp is the signed message nonce). Provide EXACTLY ONE of `apiKey` or `signature`.",
+  "minLength": 1,
+  "type": "string"
+}

Changed3 schema fields changedMay 4, 2026

removedOutput schema / properties / apiKey

Removed value: -{
-  "description": "Resolved internal API key cached in this session (if available).",
-  "type": "string"
-}

removedOutput schema / properties / sessionId / format
```
Removed value: -"uuid"
```

removedOutput schema / properties / sessionId / pattern

Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

Changed3 schema fields changedApr 29, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / properties / apiKey

Removed value: -{
-  "description": "Raw API key for internal tools login.",
-  "minLength": 1,
-  "type": "string"
-}

removedInput schema / properties / signature

Removed value: -{
-  "description": "Optional signature token in `signature_timestamp` format. Timestamp is the signed message nonce.",
-  "minLength": 1,
-  "type": "string"
-}

First observedApr 24, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only flag non-read-only, non-idempotent and open-world; the description adds substantial context beyond that: the login is bound to `mcp-session-id` server-side and must not be re-passed, the signed timestamp has a server-side age limit (default 24h) with the named `SIGNATURE_EXPIRED` failure, and an internal API key may be auto-loaded as a side effect. The security guardrail ("Never ask the user for private keys or seed phrases") is exactly the kind of behavior an agent cannot infer from structured fields.

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?

Purpose and the exclusive-or choice are front-loaded in the first clause, and every following sentence adds non-redundant information (session binding, expiry behavior, security rule). The return-shape sentence partially duplicates the existing output schema, and the single dense paragraph with semicolon-separated modes is harder to scan than a short bulleted split, but there is no filler.

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 an authentication entry point with two mutually exclusive credential paths, the description covers prerequisites (get the message first), side effects (API key auto-load, session binding), failure mode (SIGNATURE_EXPIRED), and the security constraint. Although an output schema exists, it also names the returned fields, so an agent can reason about `authMode` and `unlocked` without opening the schema.

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% and both params are documented there, so the baseline is 3; the description earns above that by explaining provenance and consequence — the signature must be produced by the user's wallet over the `message` returned by `tronsave_get_sign_message`, and each param unlocks a distinct tool set. The exclusive-or requirement is stated in both places, so that part is redundant, but the meaning of each credential is genuinely enriched.

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 ("Log in to TronSave") plus the crucial scope qualifier "for the rest of this MCP connection", which immediately separates it from per-call auth tools and from siblings like `tronsave_logout` and `tronsave_get_session_status`. The two auth modes are named with their concrete effects, so the agent knows exactly what the call accomplishes.

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?

Gives explicit routing between the two modes — `signature` unlocks wallet tools, `apiKey` unlocks internal-account tools — and names the prerequisite sibling `tronsave_get_sign_message` as the source of the message to sign. It does not state what to do if a session already exists (e.g., check `tronsave_get_session_status` before logging in, or that a repeat login replaces the session), which is the one routing 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?