Skip to main content
Glama

Get TRON Energy rental prices

get_energy_prices
Read-only

Fetches live TRON Energy prices for 65,000 and 130,000 TRX Energy over 1-hour or 1-day terms and compares them with the TRX the network would burn without Energy; no API key required.

Instructions

Live TronEnergyFrog prices for 65,000 and 130,000 TRON Energy, for 1 hour or 1 day, compared with the TRX the network would burn without Energy. No API key needed.

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": "get_energy_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context the annotations do not: live external data, fixed non-configurable tiers, and that no API key is required. It does not mention rate limits, caching/freshness behavior, or what the returned comparison looks like, which keeps it below 4.

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?

Two short sentences with no filler; scope details come first and the auth-free property closes it. Each clause carries information an agent would otherwise lack.

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 zero-argument read tool with no output schema, the definition conveys what is fetched and what it is compared against, which is enough to call it correctly. A brief note on the response shape (e.g., prices plus burn-cost delta) would make it complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters the baseline is 4. The description earns that by telling the agent the request surface is fixed — the tiers and durations are not selectable — which is meaningful given the empty schema and prevents the agent from hunting for filter arguments.

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?

The description names a specific resource (live TRON Energy rental prices from TronEnergyFrog) and pins the exact scope: two fixed tiers (65,000 and 130,000 Energy), two durations (1 hour, 1 day), plus a burn-cost comparison. An agent can tell this is a read-only pricing lookup rather than a rental or quote action. It does not explicitly contrast itself with the get_x402_rental sibling, so it stops short of a 5.

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?

Usage is only implied — the tool is clearly for checking price before deciding on a rental, but the description never states when to call this versus get_x402_rental or create_x402_quote. No exclusions or sequencing guidance are given, leaving the agent to infer routing from the sibling names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.