Skip to main content
Glama

Blazar Polygon plugin

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. Polygon only (chain 137).

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).

Output Schema

NameRequiredDescriptionDefault
txsYesSign and send in order.
fromNo
nextNo
batchNoEIP-5792 wallet_sendCalls request with the same calls (smart wallets).
quoteNo
actionYes
guardsNo
safetyNo
chainIdNo137 Polygon, 8453 Base, 1 Ethereum. BlazarForce builds are always 137.
detailsNo
signingNo
summaryYes
warningsYes
routeGuideNo
simulationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing pre-flight behavior (ownership check, simulation) and the warnings surfaced (irreversible, contract recipient, burn address). It also explains the signing handoff, which is the single most important behavioral fact for this tool. The readOnlyHint=true is consistent with building an unsigned payload rather than mutating state.

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?

Three dense sentences, front-loaded with the artifact type and followed by the signing constraint and chain restriction; nothing is padding. Minor roughness (lowercase sentence start, parenthetical warning list) keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't explain return values, and it covers the remaining gaps an agent needs: chain restriction, unsigned nature, signer limitation, and the risk warnings. Nothing material is missing for correct invocation.

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%, so all four parameters (collection, from, to, tokenId) are already documented with patterns and examples. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("Build an UNSIGNED safeTransferFrom for a BlazarForce NFT") plus the chain scope (Polygon, chain 137), which separates it from the approve/listing siblings. An agent knows exactly what artifact it gets back: an unsigned transaction, not a broadcast.

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 a decisive usage constraint: the plugin's signer refuses NFT txs, so the caller must sign with its own wallet, and the tool is Polygon-only. It does not explicitly name alternatives such as blazar_build_nft_approve for approval flows, so routing between the build_* NFT tools is left partly to inference.

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