Skip to main content
Glama

Pre-Flight EVM Tx-Simulate, Allowance Firewall & Rebalance MCP

Pre-Flight Simulate EVM Transaction for Reverts, Gas & Spend Cap

simulate_evm_tx_and_spend_firewall
Read-onlyIdempotent

Simulates any unsigned EVM transaction via eth_call + eth_estimateGas, detects dangerous unlimited ERC-20 approvals, and verifies total USD outflow against the agent's budget cap.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "simulate_evm_tx_and_spend_firewall"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoTarget contract 0x address
dataNoHex calldata (0x...)
fromNoSender wallet 0x address
chainIdNoEVM chain ID (default '8453')
valueWeiNoWei value string (default '0')
maxAllowedUsdNoRemaining spend budget in USD (default 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds real value by naming the underlying RPC methods and the two checks performed (unlimited approval detection, cumulative USD outflow vs. cap), though it never says what the tool does on a violation or whether it blocks, warns, or throws.

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?

A single sentence that front-loads the core action and then lists the two secondary checks; every clause carries distinct information and nothing is repeated from the title or annotations verbatim.

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?

No output schema exists, so the description carries the burden of explaining the return value, yet it never says what the simulation returns (revert reason, gas estimate, approval warnings, pass/fail against the cap). For a six-parameter preflight gate whose whole value is the verdict it produces, that is a meaningful omission.

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 description coverage is 100%, so every parameter including maxAllowedUsd and chainId defaults is already documented in structured form. The description's mention of the budget cap maps to maxAllowedUsd but adds no format, unit, or edge-case detail beyond what the schema says, so the baseline of 3 applies.

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?

States specific verbs and resources: simulates an unsigned EVM transaction via eth_call + eth_estimateGas, detects unlimited ERC-20 approvals, and verifies USD outflow against a budget cap. This is clearly a read-only preflight check, distinguishable from the sibling build/plan/audit tools without opening any schema.

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?

The phrase 'Simulates any unsigned EVM transaction' plus the title's 'Pre-Flight' implies the tool is used before broadcasting a transaction, but there is no explicit when-to-use or when-not guidance and no sibling is named as the alternative. Usage is inferable rather than stated.

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.