Skip to main content
Glama

Deploy a contract (testnet, opt-in)

zenith_deploy

Deploy contracts to Zenith testnet from Solidity source, Foundry/Hardhat artifacts, or bytecode; simulate cost first, then confirm to execute with automatic verification.

Instructions

Deploys a contract to Zenith testnet from a .sol file (compiled for Prague and verified automatically), a Foundry/Hardhat artifact or bytecode. Without confirm it only simulates and shows the cost. Requires a testnet key configured by the user; refuses any other chain and respects the session spend cap.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zenith_deploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
abiNoJSON ABI, with bytecode
runsNo
verifyNo
confirmNoSet true only after the user approved the simulated plan
bytecodeNo
optimizeNo
evmVersionNoprague
sourcePathNoPath to a .sol file
artifactPathNoFoundry out/X.sol/X.json or Hardhat artifact
contractNameNo
compilerVersionNo
constructorArgsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, openWorld=true, non-idempotent), the description discloses the dry-run-by-default behavior, automatic compilation for Prague and automatic verification, the mandatory testnet key, chain refusal, and enforcement of a session spend cap. These are exactly the operational traits an agent needs before invoking a network-mutating deploy.

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 tight sentences with zero filler: the accepted input forms come first, followed by the simulation gate and the hard constraints. Every clause (auto-verify, testnet-only, spend cap) contributes decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter mutation tool with no output schema, the definition covers preconditions and constraints well but says nothing about what a successful deploy returns (address? transaction hash?) beyond the simulation 'cost' hint. An agent can decide whether to call it, but not fully anticipate the result shape.

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?

With only 33% schema description coverage, the description partially compensates by explaining the three mutually alternative source inputs (sourcePath, artifactPath, bytecode), the Prague evmVersion default, and the verify behavior, plus the meaning of 'confirm'. However, abi, contractName, compilerVersion, constructorArgs, optimize, and runs remain undocumented in both places, leaving substantial ambiguity.

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?

The description opens with a specific verb and resource ('Deploys a contract to Zenith testnet') and enumerates the accepted input forms (.sol source, Foundry/Hardhat artifact, bytecode), which lets an agent distinguish it from sibling operations like zenith_verify_contract or zenith_send without opening either 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?

It gives a clear operative condition: without 'confirm' the call only simulates and reports cost, and it states prerequisites (a user-configured testnet key) plus an explicit exclusion ('refuses any other chain'). It stops short of naming an alternative sibling for mainnet deploys or verification, so it falls just shy of the top score.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.