Skip to main content
Glama
Sign In
Alchemy MCP Server

Alchemy MCP Server

Official
by alchemyplatform
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

traceRawTransaction

Simulate execution of a raw signed transaction without broadcasting. Retrieve call traces, state diffs, and logs for pre-flight verification.

Instructions

Trace a raw signed transaction without broadcasting it to the network

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": {
      "rawTransaction": "<rawTransaction>",
      "traceTypes": "<traceTypes>"
    },
    "name": "traceRawTransaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork ID. Call listSupportedNetworks for all options. e.g. "eth-mainnet", "base-mainnet"eth-mainnet
rawTransactionYesRaw transaction data
traceTypesYesArray of trace types. e.g. ["trace", "stateDiff"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It mentions 'without broadcasting' but fails to explain what tracing entails, return format, permission requirements, or potential side effects. This is insufficient for a tool with no annotations.

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 a single concise sentence that is front-loaded with the key action and resource. Every word serves a purpose with zero redundancy.

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?

While the schema covers parameter details, the description lacks information about return values, trace type options beyond the example, and whether network defaults are documented elsewhere. For a tool with 3 parameters and no output schema, this is minimally adequate but leaves gaps.

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?

The input schema has 100% description coverage for all three parameters, including examples and cross-references to listSupportedNetworks. The description adds no extra meaning beyond the schema, meeting the baseline expectation.

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 clearly states the tool traces a raw signed transaction and does not broadcast it. This verb+resource combination is specific and distinguishes it from broadcasting tools like sendTransaction. However, it does not differentiate from sibling trace tools like traceTransaction or debugTraceTransaction, which also trace without broadcasting.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like traceTransaction or debugTraceTransaction. The description merely states what it does without context on prerequisites, limitations, or recommended scenarios.

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