Skip to main content
Glama

Build NFT transfer (unsigned)

blazar_build_nft_transfer
Read-only

Build an UNSIGNED safeTransferFrom for a BlazarForce NFT after checking ownership, with a simulation and warnings (irreversible, contract recipient, burn address). the plugin's signer refuses NFT txs; sign with your own wallet.

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": {
      "collection": "<collection>",
      "from": "<from>",
      "to": "<to>",
      "tokenId": "<tokenId>"
    },
    "name": "blazar_build_nft_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient.
fromYesAddress that will sign and send the txs. Required: used for allowance checks, simulation and nonce.
tokenIdYesToken id (BlazarForce collections use 1..100).
collectionYesCollection symbol, id or address: SLPV (Sleepy Validators), STUB (Night Market Stubs), MOTH (Crystal Moths).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: it performs an ownership check, runs a simulation, and emits warnings for irreversible sends, contract recipients and burn addresses. It also explains why readOnlyHint=true holds (the result is unsigned, nothing is broadcast), which is exactly the context an agent needs.

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?

Front-loads the key fact (UNSIGNED safeTransferFrom) followed by the caveat about the plugin signer, with no filler. The first sentence is slightly run-on and has a minor article error ('an UNSIGNED'), but it stays tight.

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?

There is no output schema, so the description should say what is actually returned (the unsigned tx payload, simulation result, warnings). It hints at simulation and warnings but never states the return shape, leaving a meaningful gap for a builder tool.

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 the schema already defines each of the four parameters including the collection symbol examples and tokenId range. The description adds no further parameter-level semantics, 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?

States a specific verb and resource ('Build an UNSIGNED safeTransferFrom for a BlazarForce NFT') and distinguishes itself from write/send tools by emphasizing UNSIGNED. It does not explicitly name any sibling, but the build-prefix and 'sign with your own wallet' framing make the distinction inferable.

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?

Gives clear usage context: the plugin's own signer refuses NFT txs, so the agent must sign with its own wallet, and the tool must be used for NFT transfers specifically. It does not mention prerequisites such as needing a prior approval (compare with blazar_build_nft_approve), which is a notable gap for a transfer tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources