Skip to main content
Glama

NullClear Pre-Execution Firewall & Arbiter

nullclear_scan_token

Read-onlyIdempotent

Perform a free multi-chain (Base, Ethereum, Arbitrum, Optimism, Polygon, BSC, Solana) token security, proxy resolution, Token-2022 extension/mint/freeze authority audit, honeypot, and buy/sell tax audit (10 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).

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; auto-detects if address exists on an alternate supported chainbase
addressYesToken or contract address (0x-prefixed 42-char EVM hex, or Base58 mint address for Solana)0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"Token or contract address (0x-prefixed 42-char EVM hex for Base/ETH, or Base58 mint address for Solana)"New value: +"Token or contract address (0x-prefixed 42-char EVM hex, or Base58 mint address for Solana)"
    • changedInput schema / properties / chain / description
      Previous value: -"Target blockchain network ('base', 'eth', or 'solana'); auto-detects if address exists on an alternate supported chain"New value: +"Target blockchain network; auto-detects if address exists on an alternate supported chain"
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "base",
      -  "eth",
      -  "solana"
      -]New value: +[
      +  "base",
      +  "eth",
      +  "arbitrum",
      +  "optimism",
      +  "polygon",
      +  "bsc",
      +  "solana"
      +]
  2. Added

TDQS

A3.9/5.0
Behavior3/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 safety profile is covered. The description still adds real behavior beyond them: a rate limit (10 free calls/day/IP, no API key), a price after the quota, and the '<400 tokens' scope; but given annotations carry most of the burden, this sits at the adequate baseline rather than above it.

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?

Front-loaded with the capability, then pricing, then return shape, then the exclusion. It is a single dense, run-on sentence-cluster with some enumeration bloat (seven chain names in parentheses), but nothing is genuinely wasted.

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?

Covers the capability scope, cost/quota model, the fields returned (score, verdict, recommendedAgentAction, proxy implementation, tax percentages, LP USD, provenance block) and the sibling boundary. With no output schema, the return-value summary is a useful addition; only the paid-sibling boundary is left implicit.

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 documents both the chain enum and the EVM-hex-vs-Base58 address format, including auto-detection on alternate chains. The description repeats the chain list without adding syntax or format meaning beyond the schema, so 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?

Specific verb-plus-resource: multi-chain token security, proxy resolution, Token-2022 authority audit, honeypot and tax audit, with the chain list enumerated. It explicitly distinguishes itself from nullclear_inspect_contract for non-token selector disassembly, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear positive context (token security on seven named chains), an explicit exclusion (not for 4-byte selector disassembly on non-token contracts) and names the alternative tool. It does not explicitly contrast with nullclear_audit_paid_token; the free-vs-paid split is only hinted at by the '$0.005 USDC after 10 free calls' pricing note rather than stated as a selection rule.

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.