Skip to main content
Glama
Sign In

powersun-tron-mcp

by io.github.Hovsteder
OverviewDiscussionsAdmin

Verify Registration

verify_registration

Complete agent registration by verifying your signed challenge. Returns an API key and upgrades the current session to authenticated. After verification, all authenticated tools (buy_energy, get_balance, register_pool, etc.) will work in this session without needing to reconnect. No authentication required.

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": {
      "challengeId": "<challengeId>",
      "address": "<address>",
      "signature": "<signature>"
    },
    "name": "verify_registration"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesYour TRON wallet address (must match the register call)
signatureYesSignature from tronWeb.trx.signMessageV2(challenge, privateKey)
challengeIdYesChallenge ID from the register tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that an API key is returned, that the session is irreversibly upgraded to authenticated, and that no credentials are needed to call it. It stops short of describing challenge expiry, signature-mismatch behavior, or whether an API key can be re-obtained later, which matter for a one-shot credential-minting call.

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 sentences, front-loaded with the action and its payoff, with no filler. The closing 'No authentication required' is useful but slightly stranded at the end when it is really a precondition.

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 three-parameter credential-minting tool with no output schema, the description covers purpose, return value (API key), and the session side effect, which is what an agent most needs. The remaining gap is error and expiry behavior rather than core invocation detail.

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 description coverage is 100%, and the schema already explains that address must match the register call and that signature comes from tronWeb.trx.signMessageV2. The description adds nothing about the three parameters beyond what the schema provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and outcome: verifies a signed challenge to complete agent registration and issues an API key. The step in the flow is clear from 'Complete agent registration', but the description never names the `register` sibling that produces the challenge, so the pairing is inferred rather than stated.

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 clear context for when to call it (to finish registration and promote the current session) and notes that no authentication is required. It also explains the downstream consequence — authenticated tools like buy_energy and get_balance start working without reconnecting — but offers no guidance on what to do if verification fails or the challenge is stale.

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