Skip to main content
Glama

NullClear Pre-Execution Firewall & Arbiter

nullclear_inspect_contract

Read-onlyIdempotent

Disassemble deployed EVM bytecode across Base, Ethereum, Arbitrum, Optimism, Polygon, or BSC to resolve EIP-1967/1822/1167/Beacon/Diamond/Safe proxies, query Sourcify v2 verified ABIs, batch-resolve PUSH4 selectors via OpenChain, and analyze control-flow opcode risks (tx.origin, mutable DELEGATECALL, unguarded SELFDESTRUCT) without an Etherscan key (10 free calls/day/IP).

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 (default 'base')base
addressYes0x-prefixed 42-char EVM smart contract address0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"0x-prefixed 42-char EVM smart contract address on Base or Ethereum"New value: +"0x-prefixed 42-char EVM smart contract address"
    • changedInput schema / properties / chain / description
      Previous value: -"Target EVM chain ('base' for Base Mainnet 8453 or 'eth' for Ethereum Mainnet 1)"New value: +"Target EVM chain (default 'base')"
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "base",
      -  "eth"
      -]New value: +[
      +  "base",
      +  "eth",
      +  "arbitrum",
      +  "optimism",
      +  "polygon",
      +  "bsc"
      +]
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the description is not carrying the safety profile alone. It still adds meaningful behavior beyond them: the supported chains, the exact proxy standards auto-detected, the upstream dependencies (Sourcify v2, OpenChain), and the per-IP rate limit. It omits what the output looks like when resolution fails or when a contract is unverified, which is the remaining gap.

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?

A single front-loaded sentence that opens with the core verb and resource, then enumerates the sub-capabilities and closes with the access constraint. Dense but every clause carries information; nothing is padded or repeated.

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 multi-step inspection tool with no output schema, the description adequately covers inputs (chain set, address), the internal pipeline (proxy detection, ABI lookup, selector batching, opcode risk scan), and the quota. Missing is any indication of return shape or behavior on partial failures (e.g., unverified contract, chain-specific gaps), which matters for an aggregating tool.

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%, with both 'address' and the enum-constrained 'chain' documented in-schema, so the baseline is 3. The description restates the six chains but adds no format detail, default rationale, or validation nuance (e.g., checksum requirements, behavior on an EOA address) beyond the schema.

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?

Specific verb-plus-resource: 'Disassemble deployed EVM bytecode' followed by a concrete list of what it resolves (EIP-1967/1822/1167/Beacon/Diamond/Safe proxies, Sourcify ABIs, PUSH4 selectors, risky opcodes). An agent immediately knows the capability. It does not, however, contrast itself with near neighbors like nullclear_scan_token or nullclear_preflight_guard, so sibling differentiation is left implicit.

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?

Two practical usage conditions are embedded: it works 'without an Etherscan key' and is capped at '10 free calls/day/IP', which signals a quota-limited free tier. There is no explicit when-to-use-versus-when-to-use-an-alternative guidance, no prerequisites (e.g., does verification require a Sourcify-supported contract?), and no statement of what happens when bytecode is unverified.

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.