Skip to main content
Glama

Simulate an EVM transaction via eth_call with decoded revert

evm_simulate
Read-only

Simulates an EVM transaction execution without broadcasting: { chain, from, to, data, value }. Returns eth_call output, gas estimate, success/revert status with decoded revert reason (Error(string), Panic(uint256)), and token balance if to is an ERC-20. State overrides not supported by public RPCs. Information only, not financial advice. Related tools on this server, for a different need: evm_call when you need to read the result of a read-only EVM contract function; evm_tx when you need to check an EVM transaction's status, fee and token transfers. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "chain": "<chain>",
      "to": "<to>"
    },
    "name": "evm_simulate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget contract 42-character 0x hex address
dataNoTransaction calldata in 0x hex format
fromNoSender 42-character 0x hex address
chainYesTarget EVM chain name (e.g. ethereum, base, arbitrum)
valueNoOptional value in wei (hex or decimal string)

Output Schema

NameRequiredDescriptionDefault
toNo
fromNo
chainNo
tokenNo
sourceNo
successNo
providerNo
checkedAtNo
disclaimerNo
returnDataNo
gasEstimateNo
revertReasonNo
stateOverridesSupportedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / token
      Added value: +{}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safe-read profile is known. The description adds genuinely new behavior: nothing is broadcast, state overrides are unsupported on public RPCs, revert reasons are decoded for Error(string) and Panic(uint256), and billing is disclosed including that failed calls are free. The one remaining gap is that no rate limit or response latency/format expectation is given.

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?

The core capability and the sibling routing are front-loaded in the first sentences, and each block (inputs, outputs, limitations, price) earns its place. Minor waste comes from the boilerplate 'Information only, not financial advice' line, which does not help tool selection.

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?

An output schema exists, so the description needn't fully specify return values, and it still summarizes eth_call output, gas estimate, revert decoding and ERC-20 balance. Combined with the broadcast-free and state-override caveats plus the pricing model, this is nearly complete; only chain coverage and the payment flow's practical mechanics are left implicit.

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 coverage is 100%, so every parameter is already documented in the schema, and the description merely restates the field list { chain, from, to, data, value } without adding format or constraint detail. The only semantic addition is the note that a token balance is returned when 'to' is an ERC-20, which is about output rather than parameter meaning, 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?

The description states a specific verb and resource (simulating EVM transaction execution without broadcasting) and enumerates the exact input shape. It then explicitly distinguishes itself from the two nearest siblings, evm_call and evm_tx, by their needs, so an agent can disambiguate without opening any schema.

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

Usage Guidelines5/5

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

It routes the agent with named alternatives and the condition selecting each: evm_call for reading a read-only contract function's result, evm_tx for checking a landed transaction's status, fees and transfers. The implication is that simulate is for pre-broadcast execution preview, which is a clear when-to-use rule with no misleading gaps.

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