Skip to main content
Glama

NullClear Pre-Execution Firewall & Arbiter

nullclear_preflight_guard

Read-onlyIdempotent

All-in-one 1-call Pre-Sign Firewall across Base, Ethereum, Arbitrum, Optimism, Polygon, BSC, and Solana (10 free calls/day/IP). In one pass, recursively unwraps Multicall3/Uniswap Universal Router/Safe calldata or EIP-712 Permits or Solana wire txs, runs stateful eth_simulateV1 / Solana simulateTransaction with asset balance diffs, and automatically scans all touched token contracts for honeypots, taxes, and Token-2022 permanent delegates. Returns one deterministic recommendedAgentAction (EXECUTE_SAFE / CAUTION_HIGH_RISK / ABORT_*).

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_preflight_guard"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoTarget contract 0x address or Solana mint
dataNo0x-prefixed EVM calldata
fromNoSender 0x EVM address
chainNoTarget network (default 'base')base
valueNoNative wei amount ('0x0')
typedDataNoOptional EIP-712 typedData object (Permit, Permit2, Seaport, SafeTx) to audit before signing
transactionNoOptional Base64/Base58 serialized Solana transaction to decode and simulate
transactionsNoOptional ordered multi-tx bundle [{ to, data, value }]
stateOverridesNoOptional EVM eth_simulateV1/eth_call stateOverrides map

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, idempotent, openWorld), so the description's added value is genuine: a concrete rate limit ('10 free calls/day/IP'), the internal method (recursive unwrap of Multicall3/Universal Router/Safe, eth_simulateV1 with balance diffs, honeypot and Token-2022 delegate scanning), and a deterministic verdict shape. What it omits is failure behavior — what happens on unsupported calldata, chain-specific parameter combinations, or latency — which keeps it from a 5.

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?

Three sentences, no filler: capability and coverage first, mechanism second, return contract last. Every clause carries information. It is dense and jargon-heavy enough that an agent must parse carefully, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter tool with nested objects and no output schema, the description does the heavy lifting an agent needs: it explains the verdict values returned (EXECUTE_SAFE / CAUTION_HIGH_RISK / ABORT_*) and the free-tier limit. Gaps remain around authentication prerequisites and how partial or unsupported inputs are handled across the seven chains.

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, but the description adds real meaning by indicating the mutually exclusive input modes that the schema only lists flatly: EVM calldata vs EIP-712 permits vs Solana wire transactions vs multi-tx bundles, all handled 'in one pass'. It does not explicitly tie those modes to the typedData/transaction/transactions/stateOverrides parameter names, so a small inference step remains.

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 opens with a specific verb+resource: 'Pre-Sign Firewall' that 'recursively unwraps' calldata/permits, 'runs stateful ... simulateTransaction', and 'scans all touched token contracts'. That is far more than a restated name and makes the tool's job unmistakable. It stops short of a 5 because it never names a sibling (e.g., nullclear_simulate_transaction or nullclear_scan_token) to contrast its all-in-one scope against, leaving sibling differentiation to the reader.

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?

Usage is implied by 'Pre-Sign' and 'All-in-one 1-call', so an agent can infer this is the pre-transaction safety check. However, there is no explicit when-to-use/when-not-to-use guidance and no alternative named for narrower needs (single-chain simulation, pure calldata decoding, token scanning), despite several plausible siblings existing.

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.