Skip to main content
Glama

Blazar Polygon plugin

Approvals audit (tokens x spenders)

blazar_allowances
Read-onlyIdempotent

Audit a wallet's ERC-20 approvals on Polygon (default), Base or Ethereum (chain param): allowance() for each curated token (or tokens you pass) x each known spender (KyberSwap, LI.FI, Velora, Permit2, Uniswap, 1inch, 0x and the chain's main routers; on Polygon also BlazarFeeRouter, BlazarSwap router, staking v1/v2, QuickSwap, Sushi; or spenders you pass). Flags unlimited approvals and lists only active ones. Then use blazar_build_revoke. Read-only.

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": {
      "owner": "<owner>"
    },
    "name": "blazar_allowances"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain: "polygon" (default, chain 137), "base" (8453) or "ethereum" (1). BZB / BlazarSwap tools are Polygon only.
ownerYesWallet whose approvals to audit.
tokensNoDefault: the chain's curated token list (Polygon: the BlazarForce list).
spendersNoDefault: known routers and aggregator spenders on that chain (plus BlazarForce contracts on Polygon).

Output Schema

NameRequiredDescriptionDefault
noteNo
chainNo
ownerNo
chainIdNo
entriesNo
activeCountNo
checkedPairsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description's 'Read-only' is consistent with them. Beyond that it adds real behavioral detail: results are filtered to active approvals only and unlimited approvals are flagged, which the annotations do not convey.

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-loaded with the action and the token x spender model, and every clause carries information. The long parenthetical spender inventory makes it a dense single-sentence block rather than a cleanly structured one, but nothing is padding.

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 annotations covering safety, an output schema covering return shape, and 100% schema description coverage, the description fills the remaining gaps: chain defaults, what the default token/spender sets are, filtering behavior, and the follow-up tool. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes further by enumerating the actual default spender set (KyberSwap, LI.FI, Velora, Permit2, Uniswap, 1inch, 0x, plus Polygon-specific BlazarFeeRouter, staking v1/v2, QuickSwap, Sushi) and the default token list, which the schema only calls 'known routers'.

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 ('Audit a wallet's ERC-20 approvals'), names the chains, and defines the exact matrix being checked (allowance() per curated token x known spender). It also points forward to blazar_build_revoke, so an agent can place it in the workflow without opening the schema.

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?

Clear context for use (pre-revoke approval audit) and an explicit next step via blazar_build_revoke. It does not state exclusions or contrast with siblings like blazar_portfolio, but the scope is narrow enough that the when-to-use is unambiguous.

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