Skip to main content
Glama

estimate_energy

Read-onlyIdempotent

Simulate a smart contract call to estimate its energy consumption before sending, using contract address, function name, ABI, and optional arguments.

Instructions

Estimate energy consumption for a smart contract call (simulation).

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": {
      "address": "<address>",
      "functionName": "<functionName>",
      "abi": "<abi>"
    },
    "name": "estimate_energy"
  }
}

Input Schema

NameRequiredDescriptionDefault
abiYesContract ABI (required for encoding)
argsNoFunction arguments
addressYesContract address
networkNoNetwork name. Defaults to mainnet.
functionNameYesFunction name to call
ownerAddressNoCaller address for simulation. Defaults to configured wallet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / abi / items / additionalProperties
      Previous value: -trueNew value: +{}
  2. First observedv1.1.7

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered structurally. The description's only added behavioral signal is '(simulation)', which usefully confirms no state change occurs, but it says nothing about cost, latency, network prerequisites, or whether a valid ABI is mandatory for the estimate to succeed.

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 short sentence with zero filler and the key qualifier ('simulation') front-loaded rather than buried. It is efficient, though so terse that the parenthetical carries more weight than a whole clause should have to.

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?

With six parameters and no output schema, the description should at least characterize the return value (an energy estimate in some unit) and note the ABI-encoding prerequisite. It covers the core purpose but leaves an agent guessing what comes back and whether the estimate is network-specific.

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 one of the six parameters documented in the schema itself, so the baseline is 3. The description adds no meaning beyond the schema—it does not clarify the relationship between address/functionName/args/abi or explain what the ownerAddress simulation default implies.

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 ('Estimate') and resource ('energy consumption') scoped to smart contract calls, with '(simulation)' clarifying it does not execute. This distinguishes it well from siblings like get_energy_prices (price lookup) or update_energy_limit (mutation), though it never names an alternative explicitly.

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?

Usage is only implied: an agent can infer this is a pre-flight check before broadcasting a contract call, and '(simulation)' signals no transaction is sent. There is no explicit when-to-use/when-not-to-use guidance and no pointer to the related siblings (get_energy_prices, broadcast_transaction) it would naturally pair with.

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