Skip to main content
Glama

Simulate a transaction

simulate_transaction
Read-onlyIdempotent

Dry-runs one prepared transaction from a wallet against the latest block and explains the failure in plain language if it would revert. Steps that depend on an earlier approval only pass after that approval is mined.

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": {
      "to": "<to>",
      "data": "<data>",
      "from": "<from>"
    },
    "name": "simulate_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
dataYes
fromYes
valueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the description isn't burdened with safety disclosure. It adds real behavioral context beyond that: simulation runs against the latest block, failures are translated into plain language, and a revert may be a false negative if a prerequisite approval is not yet mined.

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 core action, and every clause (latest block, plain-language revert explanation, approval-mining caveat) carries information an agent needs. No filler or repetition of the title.

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 semantics and the main interpretation pitfall are covered, and there is no output schema obliging return-value detail. Still, for a 4-parameter tool with zero schema coverage, the absence of any parameter or input-format guidance leaves a clear gap an agent would have to guess at.

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

Parameters2/5

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

Schema coverage is 0% and no parameter is named or explained; the description only alludes to 'from a wallet' and a 'prepared transaction.' Nothing clarifies that `value` is in wei/base units, that `data` is calldata, or that `from` mirrors `to`'s address pattern, so it fails to compensate for the undocumented 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?

States a specific verb and resource: 'Dry-runs one prepared transaction from a wallet against the latest block,' plus the conditional behavior on revert. It implicitly contrasts with the build_* siblings (build creates, simulate dry-runs) but never names or explicitly distinguishes them, keeping it 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?

Usage is only implied: an agent can infer this runs before committing a transaction, but the description never says 'use before build_*/submit' or states when not to use it. The approval-dependency sentence is a caveat about interpreting results rather than selection guidance against alternatives.

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.