Skip to main content
Glama

NullClear Pre-Execution Firewall & Arbiter

nullclear_simulate_transaction

Read-onlyIdempotent

Execute stateful pre-flight simulation across EVM (eth_simulateV1 with stateOverrides, multi-tx bundles, and Transfer/Approval net asset diffs; fallback eth_call + eth_estimateGas) and Solana (simulateTransaction + wire instruction audit) BEFORE signing (10 free calls/day/IP).

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": "nullclear_simulate_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoDestination 0x smart contract address (required for single EVM call)
dataNo0x-prefixed hex calldata payload0x
fromNoSender 0x EVM address
chainNoTarget network (default 'base')base
valueNoNative wei amount as hex ('0x0') or decimal string0x0
transactionNoBase64/Base58 serialized Solana transaction when chain='solana'
transactionsNoOptional ordered multi-tx EVM bundle [{ to, data, value }]
stateOverridesNoOptional EVM stateOverrides map

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / chain / description
      Previous value: -"Target EVM chain ('base' or 'eth', default 'base')"New value: +"Target network (default 'base')"
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "base",
      -  "eth"
      -]New value: +[
      +  "base",
      +  "eth",
      +  "arbitrum",
      +  "optimism",
      +  "polygon",
      +  "bsc",
      +  "solana"
      +]
    • changedInput schema / properties / data / description
      Previous value: -"0x-prefixed hex calldata payload for the simulated call"New value: +"0x-prefixed hex calldata payload"
    • changedInput schema / properties / from / description
      Previous value: -"Sender 0x EVM address whose balance/allowance context will be simulated"New value: +"Sender 0x EVM address"
    • addedInput schema / properties / stateOverrides
      Added value: +{
      +  "description": "Optional EVM stateOverrides map",
      +  "type": "object"
      +}
    • changedInput schema / properties / to / description
      Previous value: -"Destination 0x smart contract or recipient address"New value: +"Destination 0x smart contract address (required for single EVM call)"
    • addedInput schema / properties / transaction
      Added value: +{
      +  "description": "Base64/Base58 serialized Solana transaction when chain='solana'",
      +  "type": "string"
      +}
    • addedInput schema / properties / transactions
      Added value: +{
      +  "description": "Optional ordered multi-tx EVM bundle [{ to, data, value }]",
      +  "type": "array"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "to"
      -]
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds real value beyond them: the eth_simulateV1 path with eth_call + eth_estimateGas fallback, net Transfer/Approval asset diffs, Solana wire instruction audit, and a 10 free calls/day/IP quota. It stops short of saying what a failed simulation returns or how errors surface.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with the verb first and zero filler; the parenthetical breakdown of chains and fallbacks is dense but earns its space. It is heavily jargon-packed, which slightly raises parsing cost.

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 an 8-parameter tool with zero required parameters and no output schema, the description should clarify which parameter combinations are valid per chain and what the simulation result looks like. It covers the engine and the diffs conceptually but leaves the calling contract under-specified.

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%, so the baseline is 3. The description does add semantic framing for stateOverrides and multi-tx bundles, but it never clarifies the mutual exclusivity between EVM fields (to/data/value) and the Solana 'transaction' field, which is the main ambiguity an agent faces.

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 names a specific verb and resource ('Execute stateful pre-flight simulation') and scopes it across EVM and Solana with the underlying mechanisms (eth_simulateV1, simulateTransaction). It does not explicitly distinguish itself from the sibling nullclear_preflight_guard, so an agent must infer the boundary between 'simulate' and 'guard'.

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?

'BEFORE signing' gives a clear, actionable trigger for when to reach for this tool, and the rate-limit note sets expectations. There is no guidance on when NOT to use it or which sibling to prefer for guard-style checks, leaving that comparison to inference.

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.