Skip to main content
Glama
Sign In

powersun-tron-mcp

by io.github.Hovsteder
OverviewDiscussionsAdmin

Withdraw Earnings

withdraw_earnings

Withdrawal execution is not available through MCP. Use the withdrawal flow at https://powersun.vip. This tool does not create a withdrawal request or move funds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "amount": "<amount>"
    },
    "name": "withdraw_earnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesRequested TRX amount (retained for compatibility; MCP does not execute withdrawals)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changed
    • changedInput schema / properties / amount / description
      Previous value: -"Amount to withdraw in TRX (minimum 100 TRX)"New value: +"Requested TRX amount (retained for compatibility; MCP does not execute withdrawals)"
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses the critical behavioral trait that no funds move and no request is created, which is exactly the side-effect information an agent needs for a tool whose name implies a destructive mutation.

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?

Three short sentences, zero waste, with the unavailability stated first and the redirect second. Every sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a deliberate no-op stub this is nearly complete — the agent knows not to use it and where to send the user. The one omission is what actually happens if the tool is invoked anyway (error versus a no-op response), which would help an agent recover from a mistaken call.

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

Parameters3/5

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

Schema coverage is 100% and the schema itself explains that 'amount' is retained for compatibility only, so the baseline is 3. The description reinforces that the value is inert but never names the parameter or adds any syntax or constraint detail beyond the 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 states plainly that withdrawal execution is unavailable through MCP and that this tool neither creates a request nor moves funds. This is a specific, unambiguous statement of what the tool does (nothing) and explicitly separates it from sibling tools like broadcast_transaction or execute_swap that an agent might otherwise reach for.

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?

It gives an explicit when-not-to-use plus a concrete alternative: the withdrawal flow at the named URL. An agent has no inference to do — it is told to route the user elsewhere rather than call this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All powersun-tron-mcp 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