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

NullClear — Web3 Security & Tx Decoder

Official

nullclear_scan_token

Read-onlyIdempotent

Run a free multi-chain token security, honeypot, proxy, and buy/sell tax check before trading to get a risk score, verdict, and recommended action.

Instructions

Perform a free multi-chain (Base, Ethereum, Solana) token security, EIP-1967 proxy resolution, honeypot, and buy/sell tax audit. Use this as the primary pre-trade check for any token or contract (100 free calls/day/IP, zero API key; then $0.005 USDC). Returns score, verdict, recommendedAgentAction, proxy implementation, tax percentages, LP USD, and provenance block number (<400 tokens). Do NOT use for low-level 4-byte selector disassembly on non-token contracts (use nullclear_inspect_contract) or when an EIP-712 Bazaar payment receipt is explicitly required on Base ERC-20 tokens (use nullclear_audit_paid_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_scan_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoTarget blockchain network ('base', 'eth', or 'solana'); auto-detects if address exists on an alternate supported chainbase
addressYesToken or contract address (0x-prefixed 42-char EVM hex for Base/ETH, or Base58 mint address for Solana)0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.4/5.0
Behavior4/5

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

Although annotations already declare readOnly, openWorld, idempotent, and non-destructive, the description adds real operational context: 100 free calls/day/IP with no API key, then $0.005 USDC, and a compact (<400 token) response. It does not cover error modes or latency, but the rate-limit and pricing disclosure raises it above the annotation baseline.

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 purpose and rate-limit facts are front-loaded, and the exclusions trail usefully at the end. It is dense but two sentences, with only minor redundancy between 'multi-chain' and the parenthetical chain list.

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 return fields (score, verdict, recommendedAgentAction, proxy implementation, tax percentages, LP USD, provenance block number) plus size bounds, pricing, and quota. That is sufficient for an agent to call and interpret the tool confidently.

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 the schema already documents the chain enum, the default, auto-detection, and address formats. The description adds no parameter-level detail beyond that, 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?

The description names a specific verb and resource: a multi-chain token security, proxy, honeypot, and tax audit across Base, Ethereum, and Solana. It explicitly distinguishes itself from nullclear_inspect_contract and nullclear_audit_paid_token, so an agent can route without opening schemas.

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 states the primary use case ('primary pre-trade check for any token or contract') and names two explicit exclusions with the correct alternative for each: low-level selector disassembly and EIP-712 Bazaar receipt-required audits.

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