Skip to main content
Glama

Blazar Polygon plugin

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

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the description does not contradict them — it correctly frames the output as unsigned. It adds genuinely non-structured behavior: warnings are emitted for unknown operators and approve-all, and the chain restriction to Polygon 137. It stops short of saying what the response contains or how warnings are surfaced, but with annotations covering the safety profile this is solid.

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?

Two compact sentences with the core operation front-loaded and the chain restriction kept as a short trailing constraint. Minor wording issues ('an UNSIGNED', sentence-initial lowercase) do not impede comprehension, and nothing is padding.

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 six-parameter unsigned-transaction builder with full schema coverage and an output schema, the description supplies the essential extras: unsigned nature, warning behavior, and the Polygon-only limitation. An agent has enough to call it correctly; only the revoke-vs-sibling routing and warning delivery format remain unstated.

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 coverage is 100%, so the baseline applies. The description's parameter-level content (approve(tokenId) vs setApprovalForAll, approved=false for revoke) largely restates what the schema descriptions already say, adding no new format or constraint detail beyond them.

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 is a transaction-builder rather than a broadcaster. It does not name the obvious sibling blazar_build_revoke even though it describes revoke behavior, so differentiation is left implicit.

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?

Gives two real usage constraints: the plugin's signer refuses NFT txs (so this tool is the path for NFT approvals) and it is Polygon-only (chain 137). However, it never states when to prefer this over blazar_build_revoke for the revoke case, nor any prerequisites such as required allowances or ordering relative to signing.

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