Skip to main content
Glama

transfer_crypto

Initiate crypto transfers or smart contract interactions with anti-drainer safeguards, allowance limits, destination checks, and human approval tokens.

Instructions

Initiate a crypto transfer or contract interaction. Gated by Anti-Drainer guards, zero-infinite-allowance, and human challenge tokens.

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": {
      "sourceWalletId": "<sourceWalletId>",
      "recipientAddress": "<recipientAddress>",
      "amount": "<amount>",
      "symbol": "<symbol>",
      "estimatedValueUsd": "<estimatedValueUsd>"
    },
    "name": "transfer_crypto"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesToken amount
symbolYesAsset symbol
calldataHexNoOptional raw smart contract calldata (0x...)
sourceWalletIdYesSource wallet ID (e.g. wallet_agent_gas_tank)
recipientAddressYesTarget 0x or Solana address
estimatedValueUsdYesEstimated total USD value of transaction

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose meaningful guard behavior (anti-drainer checks, allowance limiting, human challenge tokens), which is more than nothing. But it omits what happens on a blocked or failed transfer, whether the call is reversible or immediate, and what the agent should do next.

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?

Two short sentences with the purpose front-loaded and the gating constraints immediately after. Nothing is wasted, though the second sentence lists mechanisms without explaining their effect on the caller.

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?

For a high-risk write operation with no annotations and no output schema, the definition covers purpose and guard mechanisms but leaves the agent without failure handling, approval flow, or result expectations. It is minimally adequate rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the input schema already documents all six parameters with types and constraints. The phrase 'contract interaction' lightly signals that calldataHex is the path for non-transfer calls, adding a small amount of meaning beyond the schema. Baseline for full coverage is 3; the contract-interaction hint nudges it slightly up.

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: 'Initiate a crypto transfer or contract interaction', which tells an agent exactly what the tool does. It does not explicitly differentiate itself from sibling tools such as submit_crypto_approval_token or get_crypto_security_status, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied. The mention of Anti-Drainer guards, zero-infinite-allowance, and human challenge tokens suggests preconditions, but the description never states when an agent should call this versus the approval-token flow, nor what to do if a guard blocks the transfer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.