Skip to main content
Glama
NullClear — Web3 Security & Tx Decoder

NullClear — Web3 Security & Tx Decoder

Official

nullclear_simulate_transaction

Read-onlyIdempotent

Dry-run an unsigned Ethereum or Base transaction before signing to confirm success, estimate gas, decode revert reasons, and verify allowance safety.

Instructions

Execute a live eth_call and eth_estimateGas dry-run on Base or Ethereum BEFORE signing or broadcasting an unsigned transaction. Use this immediately before wallet execution when you have target to + data and need to confirm whether the call will succeed, estimate gas, and verify allowance safety (100 free calls/day/IP). Returns simulation success, gas estimate, decoded revert reason if any, and recommendedAgentAction. Do NOT use for standalone hex bytes without to or past mined tx hashes (use nullclear_decode_calldata).

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": {
      "to": "<to>"
    },
    "name": "nullclear_simulate_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination 0x smart contract or recipient address
dataNo0x-prefixed hex calldata payload for the simulated call0x
fromNoSender 0x EVM address whose balance/allowance context will be simulated
chainNoTarget EVM chain ('base' or 'eth', default 'base')base
valueNoNative wei amount as hex ('0x0') or decimal string0x0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds material context beyond them: an explicit rate limit (100 free calls/day/IP), the guarantee that nothing is signed or broadcast, and the response contents (success, gas estimate, decoded revert reason, recommendedAgentAction). The dry-run framing is consistent with readOnlyHint=true rather than contradicting it.

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?

Front-loaded with the core action and the pre-execution timing, and the negative guidance is appended rather than buried. It is a single dense paragraph that packs several ideas together, which costs a little readability but no sentence is wasted.

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?

There is no output schema, but the description enumerates the return fields, so an agent knows what to expect. Rate limits, supported chains, preconditions, and exclusions are all covered, leaving nothing essential missing for a 5-parameter read-only simulation tool.

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?

Schema coverage is 100%, so the baseline is 3. The description goes slightly further by framing `to`+`data` as the required simulation target and tying the call to 'verify allowance safety', which explains why `from` and `value` matter contextually; it does not document the `chain` enum or value format beyond what the schema already says.

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 a specific verb and resource combination ('Execute a live eth_call and eth_estimateGas dry-run') plus the two supported chains. It distinguishes itself from the sibling nullclear_decode_calldata by naming it explicitly as the wrong tool for hex-without-`to` cases.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit timing cue ('immediately before wallet execution'), a precondition ('when you have target `to` + `data`'), and concrete exclusions with the correct alternative named (use nullclear_decode_calldata for standalone hex or past mined tx hashes).

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