Skip to main content
Glama

simulate_tx

Simulate EVM or Solana transactions before broadcast to detect wallet drainers, unlimited token approvals, honeypot swaps, and MEV slippage traps.

Instructions

Pre-flight Transaction & Drainer Shield. Simulates EVM (Base, Ethereum) and Solana transactions before broadcast to detect wallet drainers, unlimited ERC-20/Permit2 approvals, honeypot swaps, and MEV sandwich slippage traps. Cost: $0.05 USDC or 0.00035 SOL.

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": {
      "chain": "<chain>",
      "tx": "<tx>"
    },
    "name": "simulate_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
txYesTransaction object (to, data, value, slippage_bps, instructions)
chainYesTarget blockchain networkbase
payment_txNoSolana signature or Base 0x transaction hash for x402 payment (0.00035 SOL or 0.05 Base USDC)
session_tokenNoPrepaid ScanPay session voucher token (sp_sess_...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and it does disclose two important behaviors: the tool simulates rather than broadcasts, and it is a paid call ($0.05 USDC / 0.00035 SOL). It does not say whether simulation touches chain state, whether there are rate limits, or how results are reported.

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 purpose and scope, ending with the price. The marketing-style label 'Drainer Shield' is followed immediately by concrete capability detail, so no sentence is wasted.

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?

For a paid tool with a nested transaction object, no annotations and no output schema, the description is only partially complete: it never says what a result looks like (risk verdict, findings list) or whether session_token substitutes for a per-call payment. It is adequate to attempt a call but leaves the agent guessing about outcomes and payment mechanics.

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?

Schema coverage is 100% and every parameter, including the nested tx object fields, is already documented in the schema. The description only reinforces the chain set (Base, Ethereum, Solana) and implies slippage_bps relevance via the MEV sandwich mention; it adds nothing about payment_tx vs. session_token usage trade-offs.

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?

Uses a specific verb (simulates) with a specific resource (EVM/Solana transactions before broadcast) and enumerates what it detects: drainers, unlimited ERC-20/Permit2 approvals, honeypot swaps, MEV sandwich slippage. An agent can immediately distinguish this pre-flight safety check from siblings like create_session_deposit or scan_code.

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 broadcast' gives a clear triggering context: run this ahead of signing/sending a transaction. It does not state exclusions or name an alternative path (e.g., what to do if the simulation flags a risk, or when to skip the check).

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