Skip to main content
Glama

Build NFT approve / revoke (unsigned)

blazar_build_nft_approve
Read-only

Build an UNSIGNED approve(tokenId) or setApprovalForAll (or a revoke with approved=false) for a BlazarForce NFT, with warnings for unknown operators and approve-all. the plugin's signer refuses NFT txs.

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>",
      "operator": "<operator>"
    },
    "name": "blazar_build_nft_approve"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNosetApprovalForAll for the whole collection.
fromYesAddress that will sign and send the txs. Required: used for allowance checks, simulation and nonce.
tokenIdNoSingle-token approve. Omit with all=true.
approvedNofalse = revoke. Default true.
operatorYesAddress allowed to move the NFT(s), e.g. a marketplace.
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

A3.7/5.0
Behavior4/5

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

Beyond the annotations it discloses genuinely useful behavior: the output is unsigned, unknown operators and approve-all raise warnings, and the plugin's own signer will not sign NFT transactions. That last point is critical context an agent cannot get from readOnlyHint/idempotentHint. It stops short of saying what the response object contains or how simulation/nonce are surfaced.

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?

One dense sentence covers all three modes plus warnings, followed by a short fragment about the signer restriction; both front-load the important facts. Slightly run-on phrasing, but no filler sentences.

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

Completeness4/5

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

For a 6-parameter unsigned-transaction builder with no output schema, the description covers the operation modes, the unsigned contract, and the signer limitation. Remaining gaps (return shape, nonce/simulation results, precedence between all and tokenId) are minor and partly absorbed by the fully documented schema.

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 each parameter already carries its own explanation. The description reinforces the semantics of tokenId, all, and approved=false as a revoke, but adds no format or interaction detail (e.g. what happens if both tokenId and all are supplied) beyond the schema.

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: builds an UNSIGNED approve(tokenId) or setApprovalForAll for a BlazarForce NFT, including the revoke variant via approved=false. An agent can tell it handles NFT approvals rather than transfers or listings, though it never names the sibling blazar_build_nft_transfer as the alternative for moving an NFT.

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 implied by the mode descriptions (single-token approve vs all=true vs revoke) and by the note that the plugin's signer refuses NFT txs, which explains why an unsigned build step is needed. There is no explicit when-to-use/when-not guidance or pointer to a sibling tool for the transfer case.

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