Skip to main content
Glama
Sign In

powersun-tron-mcp

by io.github.Hovsteder
OverviewDiscussionsAdmin

Vote for SR

trigger_vote

Vote for the best Super Representative (SR) with the highest APY to earn voting rewards. The platform automatically selects the SR with the best return. Requires VoteWitness permission granted to the platform. Voting rewards accumulate and can be claimed automatically if auto-claim is enabled. Requires API key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trigger_vote"
  }
}

Input Schema

NameRequiredDescriptionDefault
poolAddressNoPool address to vote from. If omitted, uses your first registered pool.

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 / poolAddress / maxLength
      Added value: +34
  3. Added

TDQS

A3.7/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 disclose several non-obvious traits: the SR is chosen automatically rather than by the caller, VoteWitness permission and an API key are required, and rewards accumulate with optional auto-claim. It omits what happens to existing votes on a repeat call, whether the operation costs fees/energy, and whether it 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 action and reward rationale, then prerequisites. Slight redundancy between 'highest APY' and 'best return', and the auto-claim sentence is borderline tangential but still useful context.

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?

No output schema exists, so return-value detail is not required, and the description covers the essential prerequisites and automatic-selection behavior. For an irreversible on-chain write with no annotations, a sentence on fee/cost or the effect on prior votes would have closed the remaining gap.

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 single optional parameter is fully documented in the schema, so the baseline applies. The description adds nothing about poolAddress or the default-pool fallback beyond what the schema already states.

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 ('Vote for the best Super Representative') plus the selection rule ('highest APY', 'platform automatically selects'). No sibling tool deals with voting, so there is nothing to differentiate against, but the action is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies the use case (earn voting rewards) and states prerequisites (VoteWitness permission, API key), but never says when not to use it or what to do instead, e.g. how to check or revoke existing votes.

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