Skip to main content
Glama

Blazar Polygon plugin

Batch txs into one EIP-5792 wallet_sendCalls

blazar_batch_calls
Read-onlyIdempotent

Turn txs[] from one or more build tools (same sender, same chain: Polygon 0x89, Base 0x2105 or Ethereum 0x1) into one EIP-5792 wallet_sendCalls request (version 2.0.0, atomicRequired) for smart wallets, plus the wallet_getCapabilities check to run first. Local, no network. Every build tool already returns batch for its own txs; use this to combine builds (e.g. revoke + swap).

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": {
      "txs": "<txs>"
    },
    "name": "blazar_batch_calls"
  }
}

Input Schema

NameRequiredDescriptionDefault
txsYesOrdered txs[] from build tools.
fromNoSender (smart wallet).
chainNoChain: "polygon" (default, chain 137), "base" (8453) or "ethereum" (1). BZB / BlazarSwap tools are Polygon only.

Output Schema

NameRequiredDescriptionDefault
noteNo
callsNo
methodNo
paramsNo
standardNo
summariesNo
statusCheckNo
capabilitiesCheckNo

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: it is local with no network calls, produces a version 2.0.0 atomicRequired payload, and requires a wallet_getCapabilities call first. It does not explain what happens when constraints are violated, which keeps it from a 5.

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 operation and its output format, then constraints, then the alternative-usage note. The parenthetical chain-ID list and version/atomicity block make it dense, but no sentence is filler.

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?

For a 3-parameter local transform tool with an output schema and full annotation coverage, the description supplies everything needed to call it correctly: supported chains, batch atomicity, sender/chain uniformity, the capability pre-check, and no-network behavior. Return-value details are rightly left to the output 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 the baseline is 3; the schema already documents to (null = contract creation, cannot be batched), value in wei, chainId values, and the shared-chain rule. The description reinforces the same-sender/same-chain requirement and notes BZB/BlazarSwap tools are Polygon only, but adds little that the schema does not already say.

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: turn txs[] from build tools into one EIP-5792 wallet_sendCalls request (version 2.0.0, atomicRequired), plus the wallet_getCapabilities check. It also distinguishes itself from the sibling build tools by noting that each build tool already returns its own batch and this tool exists to combine builds.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-not ("Every build tool already returns batch for its own txs; use this to combine builds") alongside a concrete positive case ("e.g. revoke + swap"). It also states the selection constraints — same sender, same chain, and that Polygon/Base/Ethereum are the only chains.

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