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

NullClear — Web3 Security & Tx Decoder

Official

nullclear_decode_calldata

Read-onlyIdempotent

Decode raw calldata, Solidity revert bytes, or mined transaction hashes to explain failures and flag malicious approvals before signing.

Instructions

Decode existing hex calldata, custom Solidity revert bytes, or a mined transaction hash to explain historical failures and flag malicious approvals. Use this AFTER a transaction failed or when auditing opaque 0x calldata bytes before signing (100 free calls/day/IP). Returns decoded 4-byte function signature, argument breakdown, revert reason, and approval-drainer warnings. Do NOT use to dry-run an unsigned transaction against live chain state (use nullclear_simulate_transaction instead).

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": {
      "input": "<input>"
    },
    "name": "nullclear_decode_calldata"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoTarget EVM chain ('base' or 'eth', default 'base')base
inputYes0x-prefixed raw hex calldata/revert bytes OR a 66-character mined transaction hash to replay

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, destructiveHint=false, so safety is covered. The description adds real value beyond them: a rate limit ('100 free calls/day/IP') and the exact return payload (4-byte signature, argument breakdown, revert reason, approval-drainer warnings) – useful because no output schema exists. Nothing contradicts the annotations.

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?

Three sentences, each earning its place: purpose first, usage timing and the output contract second, the negative routing constraint last. No filler or repeated information.

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?

With no output schema, the description compensates by enumerating the return contents, and it discloses the rate limit and chain option. For a two-parameter read-only decoder, an agent has everything needed to decide and call correctly.

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% and the schema already states the chain enum and the dual-purpose 'input' field (hex calldata or 66-character tx hash). The description restates the same input types without adding format detail, syntax, or edge-case handling beyond the schema, so the baseline 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 verb ('Decode') plus the exact resources it handles: hex calldata, custom Solidity revert bytes, or a mined transaction hash, and names the outcome ('explain historical failures and flag malicious approvals'). It is clearly distinguishable from nullclear_simulate_transaction, which it explicitly points to for the adjacent case.

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 explicit timing ('AFTER a transaction failed') and a second valid context ('auditing opaque 0x calldata bytes before signing'), plus a hard exclusion with the correct alternative: 'Do NOT use to dry-run an unsigned transaction against live chain state (use nullclear_simulate_transaction instead).' Both when and when-not are covered.

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