Skip to main content
Glama

get_chain_parameters

Read-only

Retrieve current TRON chain parameters, including Energy and Bandwidth unit prices, to check network fee rates and plan transaction costs.

Instructions

Get current chain parameters including Energy and Bandwidth unit prices. Returns structured fee information similar to gas price queries.

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_chain_parameters"
  }
}

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

A3.5/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 the safety profile is covered. The description adds that the response is 'structured fee information', which helps, but it says nothing about freshness, caching, or why idempotentHint is false for what appears to be a read-only getter.

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?

Two short sentences with the key content front-loaded and no filler. The second sentence's gas-price analogy is mildly redundant with the first but does add a useful mental model.

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 one-optional-parameter, read-only lookup with no output schema, the description covers what is returned and roughly what it resembles. Missing is any hint about response shape or which network values are accepted, but the gap is small for this complexity level.

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?

There is a single optional 'network' parameter with 100% schema description coverage (including its mainnet default), so the schema does the work. The description adds no meaning about network values or behavior beyond the default.

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 uses a specific verb and resource ('Get current chain parameters') and names concrete contents (Energy and Bandwidth unit prices), so an agent knows what it retrieves. It does not explicitly distinguish itself from near-siblings such as get_chain_info or get_bandwidth_prices, leaving overlap to be inferred.

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 phrase 'similar to gas price queries' hints at the fee-lookup use case, but there is no statement of when to choose this over get_chain_info or get_bandwidth_prices. No exclusions or prerequisites are given.

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