powersun-tron-mcp

Build Permission Transaction

build_permission_transaction

Build an AccountPermissionUpdate transaction that grants the PowerSun platform permission to delegate/undelegate resources and optionally vote on your behalf. Returns an unsigned transaction that you must sign with your private key and then broadcast using broadcast_signed_permission_tx. All existing account permissions are preserved. Requires authentication.

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": {
      "poolAddress": "<poolAddress>"
    },
    "name": "build_permission_transaction"
  }
}

Input Schema

Name	Required	Description	Default
`includeVote`	No	Include VoteWitness permission for earning SR rewards (default: true)
`poolAddress`	Yes	TRON address to grant permissions on (your pool address, T-address format)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
AddedFeb 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses authentication requirements, that existing account permissions are preserved, and that the output is unsigned and must be signed before broadcast. It omits whether repeated calls are idempotent or what happens if permissions were previously granted, which is the only remaining gap.

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 sentences, each doing work: what is built, what the caller must do next, and the safety/auth notes. The core purpose is front-loaded with no filler.

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 two-parameter unsigned-transaction builder with no output schema, the description covers return semantics, follow-up action, and permission preservation. Minor gaps remain around idempotency and error/precondition behavior, but nothing essential for correct invocation is missing.

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 both parameters are already documented in the schema, making 3 the baseline. The phrase 'optionally vote on your behalf' does add interpretive meaning to includeVote beyond the schema's 'earning SR rewards' wording, but poolAddress gets no additional context in the description.

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?

States a specific verb and resource ('Build an AccountPermissionUpdate transaction') plus the exact effect (grants PowerSun permission to delegate/undelegate and optionally vote). It is clearly separable from siblings like broadcast_signed_permission_tx and check_pool_permissions.

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?

Explicitly places the tool in a workflow: it returns an unsigned transaction, the caller must sign it, then call broadcast_signed_permission_tx. That names the alternative and the condition selecting it, though there is no explicit 'when not to use this' or prerequisite check (e.g., registration state).

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