set_active_project first. Virtual Environment tools require an active Virtual Environment, call set_active_vnet or create/fork a Virtual Environment (which auto-activates it).
You don’t need to call tools by name. Just describe what you want in natural language and Claude will pick the right tools automatically.
Project & account
These tools manage your session context. Most other tools depend on having an active project set.Networks
Contracts
Transaction simulations
Simulate and trace transactions on any Tenderly-supported EVM network without spending gas or modifying on-chain state.Core simulation tools
Simulation detail tools
After runningsimulate_transaction, resimulate_transaction, or trace_transaction, use these follow-up tools with the returned simulation_id or tx_hash to inspect specific aspects of the execution.
Virtual Environments
Create and manage private, persistent forks of public EVM networks. Virtual Environments have their own RPC endpoints and support impersonated transactions without private keys. Virtual Environment tools use a stateful session model: set a Virtual Environment as active (or create/fork one, which auto-activates it), and all subsequent Virtual Environment tools operate on it. No need to pass Virtual Environment IDs to every call.Virtual Environment simulations & traces
Simulate and trace transactions on the active Virtual Environment. These tools work with operation IDs rather than network-level tx hashes.Core Virtual Environment simulation tools
Virtual Environment simulation detail tools
Use these with theoperation_id from the tools above. They operate on the active Virtual Environment.
Advanced trace navigation
16 tools for navigating complex transactions with hundreds or thousands of internal calls. Use these whenget_simulation_call_trace or get_vnet_simulation_call_trace returns truncated results, or when you need to search, drill into, or summarize a large trace without loading the full tree.