Skip to main content
Glama

create_account

Destructive

Activates a new TRON account for a pre-generated address, using bandwidth from the configured wallet; specify the address and optional network.

Instructions

Activate a new account on the TRON network. Costs bandwidth from the configured wallet. The target address must be generated beforehand.

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

Input Schema

NameRequiredDescriptionDefault
addressYesAddress to activate (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

A4/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotentHint=false and openWorldHint=true, so the safety bar is low, yet the description still adds real behavior: bandwidth is consumed from the configured wallet and failure occurs if the address was not pre-generated. It does not state whether the result is a signed transaction or broadcast outcome, which is the remaining gap.

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?

Three short sentences, each carrying distinct information: the action, the resource cost, and the prerequisite. It is front-loaded with the action and has no redundant wording.

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 two-parameter mutation tool with rich annotations and no output schema, the description covers the key agent-facing facts — cost model and prerequisite. Only minor details, such as failure behavior or whether a transaction is returned, are absent.

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%, so both the address formats (Base58 or Hex) and the network default are already documented in the schema. The description only refers to "the target address" and adds no format or network-selection meaning beyond it; a baseline 3 is appropriate.

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?

"Activate a new account on the TRON network" gives a specific verb (activate/create) and resource (account), and the phrase about pre-generating the address implicitly separates it from generate_account. It does not explicitly name the sibling, but the concept is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The prerequisite "target address must be generated beforehand" tells the agent exactly what must precede this call, which is clear conditional context. It stops short of naming the sibling tool to call first or stating exclusions, so it falls just below a 5.

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