Skip to main content
Glama

get_node_info

Read-only

Retrieve detailed information about the current TRON node, including version, configuration, peers, and machine details, for mainnet or a specified network.

Instructions

Get detailed information about the current TRON node, including version, config, peers, and machine info.

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

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, openWorldHint, and destructiveHint=false, so safety is covered. The description adds the useful detail that the response covers the serving node's runtime/machine state, but it doesn't clarify whether 'current' means the local endpoint or the whole network, which matters given the network parameter.

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 wasted wording. It is efficient, though it could have spent a clause on disambiguation instead of yet another list item.

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 no output schema, the enumeration of returned fields is helpful, but for a diagnostic node tool the description is thin on the network scoping and on what the differing peer/machine fields look like. Adequate but with clear gaps.

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?

Only one optional parameter exists and schema coverage is 100%, so the schema already explains the network default. The description adds nothing about the network parameter, so the 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 ('Get detailed information about the current TRON node') and enumerates the content (version, config, peers, machine info), which distinguishes it from account- or transaction-oriented siblings. It does not explicitly separate itself from the close sibling get_chain_info, so it falls just short of 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 guidance on when to use this versus get_chain_info, which sounds closely related, nor any stated prerequisites. The agent must infer selection from the description alone.

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