Skip to main content
Glama

create_transaction

Idempotent

Create an unsigned TRX transfer transaction, automatically activating a missing recipient account. Returns an unsigned object for signing before broadcast.

Instructions

Create an unsigned TRX transfer transaction. The recipient account will be auto-activated if it does not exist. Returns an unsigned transaction object that must be signed before broadcasting.

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": {
      "ownerAddress": "<ownerAddress>",
      "toAddress": "<toAddress>",
      "amount": "<amount>"
    },
    "name": "create_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesTransfer amount in SUN (1 TRX = 1,000,000 SUN)
networkNoNetwork name. Defaults to mainnet.
toAddressYesRecipient address (Base58)
ownerAddressYesSender address (Base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / amount / maximum
      Added value: +9007199254740991
  2. First observedv1.1.7

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (which already declare non-read-only, open-world, idempotent, non-destructive), the description discloses two important behaviors: the recipient is auto-activated if missing, and the returned object is unsigned and must be signed before broadcast. It omits cost implications of auto-activation and any fee/energy notes, so it is strong but not exhaustive.

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: what is created, the side effect, and the required next step. It is front-loaded and has no wasted 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 four-parameter mutation tool with no output schema, the description covers purpose, the auto-activation side effect, and the return-value contract (unsigned object). Only cost/fee context and explicit sibling routing are 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% and each parameter (amount in SUN, addresses in Base58, network default) is fully documented in the schema. The description adds no parameter-level meaning beyond that, 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?

The description names a specific verb and resource ('Create an unsigned TRX transfer transaction') and implicitly separates itself from broadcast_transaction by stating the result 'must be signed before broadcasting.' It does not explicitly distinguish itself from other create_* siblings, but the resource is narrow enough that confusion is unlikely.

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?

It gives clear context: this is the step before signing and broadcasting, which tells the agent where it fits in the workflow. There is no explicit when-not-to-use guidance or named alternative, so it falls short of 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