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

NullClear — Web3 Security & Tx Decoder

Official

nullclear_inspect_contract

Read-onlyIdempotent

Inspect deployed EVM bytecode on Base or Ethereum to resolve EIP-1967/1822/1167 proxies, extract function selectors, and flag dangerous SELFDESTRUCT/DELEGATECALL opcodes without an Etherscan key.

Instructions

Disassemble deployed EVM bytecode on Base or Ethereum to resolve EIP-1967/1822/1167 proxies and extract decoded 4-byte PUSH4 function selectors without an Etherscan key. Use this for arbitrary smart contracts (vaults, routers, pools) to inspect proxy admin/implementation slots and SELFDESTRUCT/DELEGATECALL opcodes (100 free calls/day/IP). Returns isProxy, proxyType, implementationAddress, decodedFunctions, and dangerousSelectorsFound. Do NOT use for token market liquidity/honeypot tax audits (use nullclear_scan_token).

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": {
      "address": "<address>"
    },
    "name": "nullclear_inspect_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoTarget EVM chain ('base' for Base Mainnet 8453 or 'eth' for Ethereum Mainnet 1)base
addressYes0x-prefixed 42-char EVM smart contract address on Base or Ethereum0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description is not burdened with the safety profile; instead it adds genuinely non-structured facts: a 100 free calls/day/IP quota, no API-key requirement, and the exact response fields. The only gap is failure behavior (e.g. what happens for an EOA or non-contract address), which keeps it off 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?

The core action and scope are front-loaded in the first clause, and each subsequent clause adds usable information (proxy standards, rate limit, return fields, exclusion). It is dense rather than padded, though the first sentence packs several ideas together and could be split for scanability.

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?

With no output schema, listing isProxy, proxyType, implementationAddress, decodedFunctions, and dangerousSelectorsFound is exactly the right compensation, and the rate limit plus key-free operation round out what an agent needs. Only error/empty-result handling for non-contract addresses is left unspecified.

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% and both parameters carry enum/default documentation, so the schema already does the work. The description mentions the two chains and the 0x address implicitly but adds no format or edge-case guidance beyond that, matching the baseline for full-coverage schemas.

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?

The description opens with a specific verb+resource: 'Disassemble deployed EVM bytecode on Base or Ethereum', then names the concrete mechanisms (EIP-1967/1822/1167 proxy resolution, 4-byte PUSH4 selector extraction). An agent can distinguish this from the sibling decode/scan tools without reading any schema.

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?

It explicitly names the target class ('arbitrary smart contracts (vaults, routers, pools)') and gives a hard exclusion with the correct alternative: 'Do NOT use for token market liquidity/honeypot tax audits (use nullclear_scan_token)'. Both the when and the when-not are stated outright, plus the practical prerequisite (no Etherscan key needed).

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