Sairen

simulate_transaction_oracle

Simulate EVM transactions before broadcasting to detect failures, decode exact Solidity revert reasons, and estimate gas costs.

Instructions

    [Cost: $0.0010 USDC on Base & Solana] Pre-flight EVM transaction simulator & revert decoder.
    Detects if contract calls succeed or revert, decodes exact Solidity error reasons, and estimates gas costs before broadcasting.

    Actions & Parameters:
    - 'simulate': Full call execution. Params: {"to": "0x...", "from": "0x...", "data": "0x...", "value": 0, "chain": "base"|"ethereum"|"arbitrum"|"polygon"}
    - 'estimate_gas': Gas estimation. Params: {"to": "0x...", "data": "0x...", "chain": "base"}
    - 'decode_revert': Offline hex decoder. Params: {"hex_data": "0x08c379a0..."} [Free]

Input Schema

TableJSON Schema

Name	Required	Default
`action`	No	simulate
`params`	No
`payment_signature`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Sep 25, 2026

TDQS

A4.1/5.0

Behavior3/5

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

There are no annotations, so the description carries the full burden. It discloses cost, the free decode action, and the pre-flight/non-broadcasting nature of the tool, which is useful safety context. It does not explain side effects, payment_signature requirements, rate limits, or authentication needs, leaving some behavioral ambiguity.

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?

The description is compact, front-loaded with cost and purpose, and uses a clear bulleted action list. Every sentence earns its place, and the formatting makes the three operation modes easy for an agent to scan.

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?

The core simulation, gas estimation, and revert-decoding workflows are well covered, and the existence of an output schema means return values do not need to be spelled out. However, `payment_signature` is not described despite the explicit cost, and the cost line mentions 'Base & Solana' while the chain lists are EVM-only, leaving a consistency gap.

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 0% and the schema's `params` field is an untyped object with additionalProperties, so the description is the only real parameter documentation. It enumerates all three actions and their concrete parameters, including chain enums and example hex payloads, but it omits any explanation of `payment_signature`.

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, unambiguous purpose: 'Pre-flight EVM transaction simulator & revert decoder.' It names concrete actions ('simulate', 'estimate_gas', 'decode_revert') and what each does, distinguishing it from sibling tools like get_base_gas_oracle or check_address_risk.

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?

The phrase 'before broadcasting' gives clear usage context, and the action list implies when each mode is appropriate, with 'decode_revert' explicitly marked as an offline, free operation. However, it does not name alternative tools or state explicit when-not-to-use conditions.

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

Deploy Server