Skip to main content
Glama

deploy_contract

Destructive

Deploys a smart contract to the TRON network using its ABI and compiled bytecode, with optional constructor arguments, network selection, and fee limit.

Instructions

Deploy a smart contract to the TRON network using ABI and Bytecode.

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": {
      "abi": "<abi>",
      "bytecode": "<bytecode>"
    },
    "name": "deploy_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
abiYesThe contract ABI (array of objects)
argsNoConstructor arguments
nameNoContract name (optional)
networkNoNetwork name. Defaults to mainnet.
bytecodeYesThe compiled contract bytecode (hex string)
feeLimitNoFee limit in Sun (default: 1,000,000,000 = 1000 TRX)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / abi / items / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / args / items / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "items": {
      -      "type": "number"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "additionalProperties": {},
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "items": {
      +      "type": "number"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "additionalProperties": {},
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  }
      +]
  2. First observedv1.1.7

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds essentially nothing beyond that: no mention of on-chain cost, irreversibility of a deploy, network/signing requirements, or what is produced (contract address or txid). For a destructive, non-idempotent on-chain mutation this is a real gap.

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?

A single front-loaded sentence with no filler or redundancy. It is efficiently written, though the brevity is part of why behavioral context is thin.

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?

Placeholder correction: given no output schema exists, the description should ideally state the deploy result (address/txid) and cost implications, which it omits. Combined with 6 parameters and a destructive on-chain effect, it leaves meaningful gaps, so this is incomplete relative to tool complexity.

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 every parameter documented including defaults for network and feeLimit. The description only restates the two required parameters (ABI, bytecode) and adds no format, constraint, or interaction detail beyond the schema. Baseline 3 applies.

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: deploy a smart contract to the TRON network, and names the two required inputs (ABI, bytecode). An agent can tell this is a write/deployment action rather than a read. It does not explicitly contrast with siblings like create_transaction or broadcast_hex, but the purpose itself is unambiguous.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites (compiled bytecode, funded account, signing), and no alternatives named. Nothing tells the agent whether to prefer this over create_transaction or broadcast_hex for contract deployment.

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

Deploy Server

Other Tools