Skip to main content
Glama

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.

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false; the description reconciles and extends that by explaining it only constructs an unsigned tx and never broadcasts, and by disclosing that a simulation and verification settings are included in the result. With no output schema, this is meaningful behavioral information, though it is silent on nonce/allowance implications of the 'from' address and on rate or gas-side caveats.

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?

Two sentences, tightly packed with no filler, and the key constraint ('Never deploys') is placed before the routing sentence. Every clause carries distinct information.

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 2-parameter builder with full schema coverage and no output schema, the definition covers the critical facts: unsigned output, simulation included, and template-driven params. The phrase 'verification settings' is left unexplained, which is a minor gap given no output schema exists to clarify it.

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 both top-level fields and every per-template field are already documented in-schema. The description only adds that parameters are 'named per template,' which the oneOf structure already conveys, so baseline 3 is appropriate.

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 an UNSIGNED contract-creation tx') and enumerates exactly what comes back: named parameters per template, predicted address, eth_call creation simulation, and verification settings. 'Never deploys' plus the two named templates (agent token, staking pool) separate it from the deploy/simulate siblings without needing their schemas.

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?

'Use for launching an agent token or a staking pool on Polygon' gives a clear trigger, and 'Never deploys' implies the build-then-deploy workflow. It stops short of naming the follow-up tool (e.g. blazar_deploy_templates) or stating exclusions, so the agent must infer the next step.

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