Skip to main content
Glama

get_energy_prices

Read-only

Query historical TRON energy unit prices by network to compare past costs and plan transactions or staking decisions.

Instructions

Query historical energy unit price on the TRON network.

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
networkNoNetwork name. Defaults to mainnet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.1.7

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so this tool's safety profile is covered. The description contributes only the 'historical' scope and the TRON network binding; it says nothing about the time window returned, granularity, pagination, or why idempotentHint is false for a read-only query.

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?

A single front-loaded sentence with no filler. The brevity is appropriate, though it edges toward under-specification rather than tight completeness.

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?

With one optional parameter and no output schema, the tool is simple, but the description leaves a real gap: 'historical' with no time-range parameter or stated return window makes the result shape unpredictable, and there is no output schema to compensate.

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% for the single optional 'network' parameter, so the baseline is 3. The description adds no information about valid network values or what defaults mean 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?

The description gives a specific verb and resource: 'Query historical energy unit price on the TRON network.' The word 'energy' implicitly distinguishes it from the sibling get_bandwidth_prices, but the description never explicitly contrasts the two, 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 Guidelines2/5

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

There is no when-to-use guidance, no when-not-to-use guidance, and no mention of alternatives such as estimate_energy or get_bandwidth_prices. The only cue is the adjective 'historical', which the agent must interpret on its own.

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

Deploy Server

Other Tools