Skip to main content
Glama
Sign In

powersun-tron-mcp

by io.github.Hovsteder
OverviewDiscussionsAdmin

Buy Energy

buy_energy

Purchase TRON Energy for a target address. Creates a MARKET order that will be filled by available pools. Deducts cost from your balance.

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": {
      "targetAddress": "<targetAddress>",
      "txCount": "<txCount>"
    },
    "name": "buy_energy"
  }
}

Input Schema

NameRequiredDescriptionDefault
txTypeNoTransaction type (default: trc20_transfer)
txCountYesNumber of transactions you need energy for
resourceTypeNoResource type (default: ENERGY)
targetAddressYesTRON address to delegate energy to (T-address format)
durationMinutesNoDuration in minutes. Allowed: 2, 5, 10, 15, 30, 60, 180, 360, 1440, 10080, 43200. Default: 60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / txCount / maximum
      Added value: +9007199254740991
  2. Changed1 schema field changed
    • changedInput schema / properties / durationMinutes / description
      Previous value: -"Duration in minutes. Allowed: 2, 5, 10, 15, 30, 60, 360, 1440, 10080, 43200. Default: 60."New value: +"Duration in minutes. Allowed: 2, 5, 10, 15, 30, 60, 180, 360, 1440, 10080, 43200. Default: 60."
  3. Changed1 schema field changed
    • addedInput schema / properties / targetAddress / maxLength
      Added value: +34
  4. First observed

TDQS

B3.4/5.0
Behavior3/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 it does disclose two important traits: the order is a MARKET order filled by available pools, and cost is deducted from the caller's balance. However, it omits slippage/pricing behavior, whether the order can partially fill or fail, and what permissions or preconditions are required for a financial mutation.

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 resource, then the order mechanics, then the balance impact – no filler. The only minor redundancy is restating the tool name, but the balance-deduction sentence earns its place.

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

Completeness3/5

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

For a five-parameter financial mutation with no annotations and no output schema, the definition covers what the tool does and that it costs balance. It still leaves an agent unsure about return values (order ID? filled amount?), pricing/slippage, and failure modes, which matters for a spend operation.

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%, including enum values and the allowed duration list, so the schema already documents all five parameters. The description only echoes target address and implicitly ties txCount to energy needs, adding no format or semantics beyond the structured fields; baseline 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 resource ('Purchase TRON Energy for a target address') and adds the order type ('Creates a MARKET order that will be filled by available pools'), which is far more informative than the title alone. It does not explicitly name which sibling to use instead for quoting or estimating (e.g. estimate_cost, get_swap_quote), so differentiation is implied 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 Guidelines3/5

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

The description implies the use case – you need energy delegated to an address and want an immediate market fill – but never says when to use this versus get_available_resources, estimate_cost, or get_pool_delegations. The market-order detail hints at immediacy versus some other order type, yet no exclusions or prerequisites (balance, registration, permissions) are given.

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