Skip to main content
Glama

update_energy_limit

Destructive

Updates a smart contract’s origin energy limit to cap the energy its creator pays per execution; requires the creator’s wallet and a positive energy value.

Instructions

Update a contract's originEnergyLimit (max energy the contract creator will pay per execution). Requires the contract creator's wallet.

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": {
      "contractAddress": "<contractAddress>",
      "originEnergyLimit": "<originEnergyLimit>"
    },
    "name": "update_energy_limit"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.
contractAddressYesThe contract address
originEnergyLimitYesNew originEnergyLimit value (energy units, must be > 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.1.7

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the authorization requirement (creator's wallet) and the economic meaning of the limit (max energy the creator pays per execution). It still doesn't say whether the change is reversible or what happens to in-flight executions.

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, front-loaded with the action and target, with the prerequisite stated last where it is easy to scan. Every clause carries information; nothing is redundant.

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 three-parameter mutation with full schema coverage, no output schema, and annotations that already flag destructiveness, the definition covers the action, the field's meaning, and the auth requirement. The remaining gap is the lack of any statement about reversibility or the effect of the change on the contract's runtime behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks by explaining that originEnergyLimit is the maximum energy the contract creator will pay per execution — something the schema only labels as a number in energy units. The network parameter's mainnet default is left to 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?

The description names a specific verb and resource ("Update a contract's originEnergyLimit") and explains what the field means in a parenthetical, so the agent knows the exact mutation. It does not distinguish itself from nearby siblings such as update_contract_setting, so it falls short of a 5.

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?

It supplies one concrete prerequisite — "Requires the contract creator's wallet" — which tells the agent whose credentials to use. It gives no explicit when-to-use/when-not guidance and never names an alternative tool for adjusting contract settings, so usage is only implied.

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