Skip to main content
Glama
Sign In
waiaas

waiaas

by waiaas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

transfer_nft

Transfer an NFT to a specified recipient address. Supports ERC-721, ERC-1155, and Metaplex standards on EVM and Solana networks.

Instructions

Transfer an NFT (ERC-721/ERC-1155/Metaplex) to a recipient address. Default tier: APPROVAL.

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>",
      "token_address": "<token_address>",
      "token_id": "<token_id>",
      "standard": "<standard>",
      "network": "<network>"
    },
    "name": "transfer_nft"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient address (0x-hex for EVM, base58 for Solana).
token_addressYesNFT contract address (EVM) or mint address (Solana).
token_idYesToken ID within the contract (EVM). Use "0" for Solana Metaplex.
standardYesNFT standard.
networkYesNetwork identifier (e.g., "ethereum-mainnet", "solana-mainnet" or CAIP-2 "eip155:1").
amountNoNumber of tokens to transfer (default: "1"). Only relevant for ERC-1155 multi-copy NFTs. This is a count, not a smallest-unit value.
wallet_idNoTarget wallet ID. Required for multi-wallet sessions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.11.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden. It only mentions 'Default tier: APPROVAL', which is vague and does not explain the approval process, gas costs, idempotency, or error conditions. The behavioral traits are insufficiently disclosed.

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?

The description is a single sentence with a supplementary note, making it very concise. However, it lacks structured sections (e.g., usage, behavior) that could improve scannability.

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?

Given the tool's complexity (7 parameters, no output schema, no annotations), the description is too brief. It omits information about return values, error handling, network prerequisites, and the approval workflow, leaving significant gaps for the agent.

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?

The input schema has 100% coverage, each parameter is clearly described. The description adds no additional semantic value beyond what the schema already provides, so the baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the action (transfer), the resource (NFT), and the specific standards (ERC-721, ERC-1155, Metaplex). This verb+resource+standards combination makes the tool's purpose distinct from siblings like send_token or approve_token.

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?

No guidance on when to use this tool versus alternatives (e.g., send_token for fungible tokens, approve_token for approvals). The description does not mention prerequisites, when not to use, or direct the agent to other tools for related tasks.

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