Skip to main content
Glama

get_account_net

Read-onlyIdempotent

Retrieve bandwidth (net) resource information for a TRON account by address, with optional network selection defaulting to mainnet.

Instructions

Get bandwidth (net) resource information for an account.

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": {
      "address": "<address>"
    },
    "name": "get_account_net"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesAccount address (Base58 or Hex)
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.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered without the description. The description's only added value is equating 'net' with bandwidth, a useful domain clarification, but it says nothing about network-default behavior, failure modes for an unknown address, or response shape.

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?

A single front-loaded sentence with no filler, restatement of the title, or hedging. Every word carries information and nothing is wasted.

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?

This is a simple two-parameter read tool with full schema coverage and rich annotations, so the bar is low, but the description still leaves the resource concept ambiguous relative to siblings like get_account_resource and get_account_balance. An agent knows how to call it but not confidently why it would choose it over the sibling.

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%, with both 'address' (Base58 or Hex) and 'network' (defaults to mainnet) documented in the schema itself. The description adds no format, default, or constraint information beyond that, so the baseline of 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 bandwidth (net) resource information for an account', and the parenthetical clarifies that 'net' means bandwidth. It does not differentiate from the sibling get_account_resource, which an agent could reasonably assume covers the same data, so the sibling boundary is left unstated.

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 prerequisite for the required address, and no mention of when to prefer get_account_resource or get_account_info instead. The agent must infer the usage context entirely from the tool name and schema.

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