Skip to main content
Glama

what_if

Replay a real historical transaction with modified fields (Amount, Destination, etc.) to see what would have happened at the original ledger state.

Instructions

TIME MACHINE — counterfactual replay of a REAL historical transaction: fetch it by hash, apply your field overrides (different Amount, Destination, params, ...), then run the full flight simulator AT THAT HISTORICAL LEDGER (hooks, state and parameters as they were). Answers 'what would have happened if this tx had been X?'. Read-only; nothing is signed or submitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
txHashYesreal validated transaction hash
networkNomainnet
overridesNofields to change on the tx before re-simulating (e.g. {"Amount": "99000000"})

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
notesNo
caveatNo
summaryNo
verdictNo
hookRunsNo
scamScoreNo
baseTxHashNo
historicalNo
transactorNo
ledgerIndexNo
staticChecksNo
overriddenFieldsNo
Behavior5/5

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

Given no annotations, the description fully discloses behavior: fetches a transaction, applies overrides, runs simulation at the historical ledger with hooks and state as they were, and is read-only. No contradictions or hidden effects.

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 concise, front-loaded with 'TIME MACHINE', and packs the essential idea into two clear sentences without extraneous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the existence of an output schema and the simplicity of input parameters, the description covers the necessary context: what it does, how overrides work, and that it operates on a historical ledger. No gaps remain.

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?

The description adds value beyond the schema by explaining the override object with examples (Amount, Destination). While the schema covers 2 out of 3 parameters, the description clarifies the overall flow and intent.

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 clearly states it performs a counterfactual replay of a real historical transaction on its original ledger. It distinguishes from siblings like simulate_hook_trigger or simulate_transaction by specifying the historical context and read-only nature.

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?

It notes the tool is read-only and nothing is signed, which guides usage. However, it doesn't explicitly state when to use this versus similar simulation tools, nor does it list prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Hugegreencandle/xahau-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server