Skip to main content
Glama

TronSave MCP Server

by io.tronsave.mcp
OverviewDiscussionsAdmin

Revoke API Key

tronsave_revoke_api_key
DestructiveIdempotent

Revoke the caller's current internal API key. Side effect: any future request using the previous key is rejected. Existing in-flight sessions cached by the server may continue serving until their TTL expires — treat the effect as 'best-effort immediate' rather than guaranteed instantaneous cutoff. Idempotent — revoking an already-revoked key returns success. Requires a signature session and mcp-session-id. Call tronsave_generate_api_key afterwards to mint a replacement when continued internal access is needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesGraphQL mutation status code (HTTP-like; `0`/`200` indicates success). Always pair with `success` for routing.
dataYesFor `generateApiKey`: the freshly issued internal API key — treat as SECRET, store securely. For `revokeApiKey`: server-defined confirmation string (no key material).
messageYesHuman-readable status text. Populated even on success; localized error messages may appear here on failure.
successYesWhether the mutation succeeded at the backend level. Always check this before reading `data`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed4 schema fields changed
    • 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 / data / description
      Added value: +"For `generateApiKey`: the freshly issued internal API key — treat as SECRET, store securely. For `revokeApiKey`: server-defined confirmation string (no key material)."
    • 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`."
  4. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations only indicate idempotent and destructive. Description adds crucial context: in-flight sessions may continue until TTL, key is best-effort immediate, and requires a signature session. This fully discloses behavior beyond annotations.

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 sentences, each adding value: purpose, side effect, idempotency, follow-up action. No fluff, well-structured and front-loaded.

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?

The description fully explains behavior, side effects, prerequisites, and post-action guidance. Given no parameters and an output schema exists, it is complete for selection and invocation.

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

Parameters5/5

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

With 0 parameters, the schema already covers all. However, the description adds that the tool requires a signature session and mcp-session-id (implicit context), providing meaning beyond the empty 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 clearly states 'Revoke the caller's current internal API key', which is a specific verb-resource pair. It is distinct from sibling tools like tronsave_generate_api_key, which creates a key.

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 states when to use (revoke current key) and recommends calling tronsave_generate_api_key afterwards for replacement. Also notes that effect is best-effort immediate, not instantaneous, guiding appropriate usage.

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 toolsInspect
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