Skip to main content
Glama

Blazar Polygon plugin

Build deploy tx (ERC-20 or staking pool)

blazar_build_deploy
Read-only

One call to build an UNSIGNED contract-creation tx for a template, with named parameters per template, the predicted address, a simulation (eth_call creation) and verification settings. Never deploys. Use for launching an agent token or a staking pool on Polygon. 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": {
      "from": "<from>",
      "params": "<params>"
    },
    "name": "blazar_build_deploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesAddress that will sign and send the txs. Required: used for allowance checks, simulation and nonce.
paramsYesTemplate and its named parameters.

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.8/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, so the safety profile is partly covered. The description adds genuinely new behavior: the tx is unsigned (never broadcast), it returns the predicted contract address, includes an eth_call creation simulation, and carries verification settings. Idempotency and the nonce/allowance dependency of 'from' are left to schema and annotations.

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, front-loaded with the action and the 'Never deploys' caveat, then usage, then network scope. No filler and nothing repeated from annotations or schema.

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?

Output schema exists, so return values needn't be enumerated, yet the description still previews predicted address and simulation. Chain restriction and the signed-vs-unsigned boundary are covered, which are the main failure modes for a build-tx tool. Only the sibling overlap with the v2 staking builder is unaddressed.

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%, with per-template fields fully documented including units ('HUMAN units, 18 decimals') and constraints. The description adds only the framing that parameters are named per template via oneOf variants, which is marginal above 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 contract-creation tx for a template, for ERC-20 or staking pool. This clearly separates it from blazar_deploy_templates (which presumably broadcasts) and from blazar_decode_tx/blazar_simulate_tx. It stops short of naming blazar_build_staking_v2, whose overlap with 'a staking pool' is left unaddressed.

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 a positive use case ('launching an agent token or a staking pool on Polygon') and a hard constraint (Polygon chain 137 only). However, it offers no exclusions and does not distinguish itself from blazar_build_staking_v2, so an agent must infer which staking-pool builder applies.

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