Skip to main content
Glama

NullClear Pre-Execution Firewall & Arbiter

nullclear_decode_calldata

Read-onlyIdempotent

Decode EVM calldata (recursively unwrapping Multicall3, Uniswap Universal Router, Safe execTransaction), EIP-712 typed-data signatures (Permit, Permit2, Seaport), Solana wire transactions (Base64/Base58), custom Solidity revert bytes, or mined tx hashes with verified-router spender trust classification (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_decode_calldata"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoTarget network (default 'base')base
inputNo0x-prefixed hex calldata/revert bytes, 66-char tx hash, or Base64/Base58 Solana transaction
typedDataNoOptional EIP-712 typedData JSON (Permit, Permit2, Seaport, SafeTx)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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 / input / description
      Previous value: -"0x-prefixed raw hex calldata/revert bytes OR a 66-character mined transaction hash to replay"New value: +"0x-prefixed hex calldata/revert bytes, 66-char tx hash, or Base64/Base58 Solana transaction"
    • addedInput schema / properties / typedData
      Added value: +{
      +  "description": "Optional EIP-712 typedData JSON (Permit, Permit2, Seaport, SafeTx)",
      +  "type": "object"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "input"
      -]
  2. Added

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, non-destructive and open-world, so the safety profile is covered. The description still adds real context beyond that: recursive unwrapping of Multicall3 / Universal Router / Safe execTransaction, spender trust classification via verified routers, and a hard rate limit of 10 free calls/day/IP.

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?

A single dense sentence that front-loads the verb and the highest-value capability, with the rate limit placed last. It borders on a run-on list, but every clause carries information rather than filler.

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 read-only decoder with no output schema, the description covers accepted input types, supported protocols and the rate limit, which is most of what an agent needs. It stops short of describing the shape of the decoded response or how trust classification is reported, but nothing is misleading.

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 chain, input and typedData are already documented with their accepted formats and the chain enum. The description largely restates those formats (Permit, Permit2, Seaport, Base64/Base58) without adding syntax or precedence rules, so the baseline of 3 is appropriate.

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 (Decode) plus an enumerated set of resource types: EVM calldata, EIP-712 typed data, Solana wire transactions, revert bytes and tx hashes. That enumeration makes it clearly distinct from siblings like inspect_contract or simulate_transaction, which operate on contracts/transactions rather than raw byte blobs.

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 input formats listed (0x hex, 66-char tx hash, Base64/Base58 Solana tx) imply when the tool applies, and the free-tier rate limit is stated. However there is no explicit when-to-use/when-not guidance and no named alternative for overlapping tasks such as simulation or contract inspection.

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.