Skip to main content
Glama

transfer_trx

Destructive

Send TRX to a recipient address on TRON by specifying the amount and optional network.

Instructions

Transfer TRX to an address.

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": {
      "to": "<to>",
      "amount": "<amount>"
    },
    "name": "transfer_trx"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient address
amountYesAmount to send in TRX (e.g., '10.5')
networkNoNetwork name. Defaults to mainnet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / required
      Previous value: -[
      -  "to"
      -]New value: +[
      +  "to",
      +  "amount"
      +]
  2. First observedv1.1.7

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is conveyed structurally. The description adds nothing beyond that: it does not mention irreversibility, network fees, confirmation requirements, or what happens on failure. For a destructive value-transfer operation, that is a meaningful gap even with annotations present.

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 short sentence with the action front-loaded and zero wasted words. It is efficient, though the terseness borders on under-specification rather than optimal density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, non-idempotent, open-world mutation with no output schema, and the description provides no information about fees, confirmation, network selection implications, or failure modes. The schema covers parameters well, but the behavioral context an agent needs before firing an irreversible transfer is missing.

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 the meaning of `to`, `amount`, and `network` is already fully documented in the schema, including the amount format and mainnet default. The description adds no extra semantics beyond restating the recipient concept, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Transfer TRX"), so the basic action is unambiguous. However, it does not distinguish this from sibling tools like transfer_trc20 or broadcast_transaction, leaving the agent to infer that TRX is the native coin and not a token. Purpose is clear but not differentiated.

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 tool versus transfer_trc20, broadcast_transaction, or create_transaction. No prerequisites (funded account, key availability), no exclusions, and no conditions are stated. The agent must infer usage entirely from the tool name.

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