Skip to main content
Glama
Sign In

powersun-tron-mcp

by io.github.Hovsteder
OverviewDiscussionsAdmin

Register Selling Pool

register_pool

Register a TRON address as an energy/bandwidth selling pool on PowerSun. This creates a pool and auto-selling configuration. After registering, you must grant active permissions to the platform address (DelegateResource, UnDelegateResource, VoteWitness) so the platform can delegate resources to buyers and vote on your behalf. Use check_pool_permissions to verify permissions after granting them. Requires API key.

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": {
      "paymentAddress": "<paymentAddress>"
    },
    "name": "register_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
autoVoteNoAuto-vote for the best Super Representative to earn rewards (default: true)
sellEnergyNoEnable energy selling (default: true)
sellBandwidthNoEnable bandwidth selling (default: false)
paymentAddressYesTRON address to register as pool (starts with T, 34 characters). This is the address where you hold/stake TRX.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changed
    • addedInput schema / properties / paymentAddress / maxLength
      Added value: +34
  3. 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 the side effect (pool plus auto-selling config created), the auth requirement (API key), and the security-relevant consequence (platform can delegate resources and vote on the user's behalf). It omits idempotency, error behavior for an already-registered address, and whether registration is reversible.

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?

Front-loaded with the purpose, then the required follow-up steps, then the auth note. Four sentences with essentially no filler; the closing 'Requires API key' is slightly tacked-on but still load-bearing.

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?

There is no output schema, so an agent would ideally know what registration returns (pool ID, address), which is absent. However, for a 4-parameter mutation tool the essential operational context — prerequisites, downstream permission grants, verification path, and auth — is all present.

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%, so the schema already documents paymentAddress and the three boolean toggles with defaults. The description only hints at 'auto-selling configuration' without mapping to sellEnergy/sellBandwidth/autoVote, so it adds little beyond structured fields — baseline 3.

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 resource: 'Register a TRON address as an energy/bandwidth selling pool on PowerSun', and adds that it creates both a pool and an auto-selling configuration. It does not explicitly distinguish itself from the sibling tool named 'register', but the resource and effect are unambiguous.

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 the post-registration workflow (grant DelegateResource, UnDelegateResource, VoteWitness active permissions to the platform address) and routes verification to check_pool_permissions. It also flags the API-key prerequisite. What is missing is a when-not clause, e.g. what to do if the address is already registered.

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