Skip to main content
Glama

Blazar Polygon plugin

Build revoke txs (approve to 0), simulated

blazar_build_revoke
Read-only

Build UNSIGNED revoke txs (approve(spender, 0)) on Polygon (default), Base or Ethereum (chain param) for 1-10 token/spender pairs, each simulated from the owner, with the current allowance and gas. Feed it the active entries from blazar_allowances. Returns txs[] plus batch (EIP-5792) to revoke several in one smart-wallet call.

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": {
      "from": "<from>",
      "revokes": "<revokes>"
    },
    "name": "blazar_build_revoke"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesAddress that will sign and send the txs. Required: used for allowance checks, simulation and nonce.
chainNoChain: "polygon" (default, chain 137), "base" (8453) or "ethereum" (1). BZB / BlazarSwap tools are Polygon only.
revokesYes1-10 token/spender pairs, e.g. the active entries from blazar_allowances.

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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this by stressing the output is UNSIGNED and only simulated from the owner. It adds genuinely useful behavior not in the annotations: per-pair simulation, inclusion of current allowance and gas, and a returned txs[] plus EIP-5792 batch for multi-revoke in one smart-wallet call.

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?

Three tight sentences with no filler: output artifact and call signature first, then chains and pair limits, then the upstream source and return shape. Every clause carries operational information an agent needs before invoking.

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, annotations covering safety hints, and full parameter coverage, the description supplies exactly the missing context: that the txs are unsigned and simulated, which upstream tool feeds it, and that a batch payload is returned. Nothing required to call it correctly is absent.

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 from, chain, revokes, token and spender are all documented in structured form, including the enum chain values and the token resolution rules. The description largely restates these (default chain, 1-10 pairs) without adding syntax or format 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 UNSIGNED revoke txs (approve(spender, 0))'), the exact chains supported, and the 1-10 token/spender pair scope. The parenthetical call signature and the 'approve to 0' framing make it distinguishable from sibling builders such as blazar_build_swap or blazar_build_nft_approve.

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 an explicit upstream routing instruction: 'Feed it the active entries from blazar_allowances', which tells the agent where the revoke list comes from. It also states the default chain, so an agent knows polygon applies when chain is omitted; it does not, however, name an alternative to use when revoking NFT approvals instead of token allowances.

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