Skip to main content
Glama

transfer_trc20

Destructive

Transfer TRC20 tokens to a recipient address by specifying the token contract address, recipient, and amount; optionally select the network, which defaults to mainnet.

Instructions

Transfer TRC20 tokens 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": {
      "tokenAddress": "<tokenAddress>",
      "to": "<to>",
      "amount": "<amount>"
    },
    "name": "transfer_trc20"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient address
amountYesAmount to send (raw amount with decimals)
networkNoNetwork name. Defaults to mainnet.
tokenAddressYesThe TRC20 token contract address

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: -[
      -  "tokenAddress",
      -  "to"
      -]New value: +[
      +  "tokenAddress",
      +  "to",
      +  "amount"
      +]
  2. First observedv1.1.7

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: no note that the transfer is irreversible, that funds move on mainnet by default, or what happens on failure. It is a pure restatement of the action.

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 zero redundant wording. Its brevity is a virtue structurally, even though the same brevity causes gaps elsewhere.

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 fund-moving mutation with no output schema and no annotation-level detail about confirmation, fees, or failure modes. Given the stakes of an irreversible token transfer, the description should say more than one sentence about prerequisites and consequences.

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 all four parameters (to, amount, network, tokenAddress) are already documented in the schema. The description adds no meaning beyond it, 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?

The description states a specific verb and resource ('Transfer TRC20 tokens') that an agent can distinguish from the TRX-native sibling transfer_trx. It stops short of explicitly naming alternatives or scope boundaries, but the resource 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 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 instead of transfer_trx, create_transaction/broadcast_transaction, or approve flows, and no preconditions such as sufficient token balance, energy, or address validation. The agent must infer all routing decisions from the tool name 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