Fuse Network

Smart-account: transfer NFT

fuse_smart_transfer_nft

Submits an ERC-4337 UserOperation transferring an NFT (ERC-721 / ERC-1155) from the configured smart wallet to a recipient.

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": {
      "nftContractAddress": "<nftContractAddress>",
      "to": "<to>",
      "tokenId": "<tokenId>"
    },
    "name": "fuse_smart_transfer_nft"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Recipient address.
`tokenId`	Yes	NFT token ID (decimal or 0x-prefixed hex string).
`nftContractAddress`	Yes	ERC-721 / ERC-1155 contract address.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 28, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It notes the tool submits a UserOperation, but fails to mention important traits like required approvals, gas costs, reversibility, or success conditions. The minimal detail leaves significant gaps for an agent.

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?

The description is a single, front-loaded sentence that states the action, mechanism, and target. Every word serves a purpose with no redundancy. Efficient and clear.

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 tool with moderate complexity (smart account, user ops) and simple schema without output schema, the description is adequate but misses details about prerequisites (e.g., approval), return value (likely userOp hash), and smart wallet configuration. It provides the core function but lacks completeness.

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 covers 100% of parameters, each with descriptions. The tool description does not add additional meaning beyond what the schema already provides. Per rubric, baseline is 3 when coverage is high, and the description does not enhance parameter understanding.

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 uses specific verb 'submits' and resource 'NFT', clearly indicating it transfers NFTs (ERC-721/ERC-1155) via ERC-4337 UserOperation from the smart wallet to a recipient. It distinguishes well from sibling tools like fuse_smart_transfer_token (ERC20) and fuse_send_native.

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?

The description provides clear context for transferring an NFT from a smart wallet, but does not explicitly state when to use this tool versus alternatives like fuse_smart_approve_nft or fuse_smart_call_contract. No exclusions or prerequisites are mentioned, leaving the agent to infer usage.

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

All Fuse Network tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?