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

NullClear — Web3 Security & Tx Decoder

Official

nullclear_audit_paid_token

Read-onlyIdempotent

Runs NullClear's x402 Bazaar paid oracle for Base ERC-20 tokens, returning a signed EIP-712 clearing receipt with LP and bytecode verification when a settlement receipt is required.

Instructions

Run NullClear's x402 Bazaar paid oracle for Base Mainnet (8453) ERC-20 tokens returning a cryptographically signed clearing receipt (10 free trial calls/day, then $0.005 USDC). Use this ONLY when you specifically require a Base Bazaar EIP-712/keccak256 settlement receipt alongside token LP and bytecode verification. For free (100/day) multi-chain Base/ETH/Solana token & proxy scanning, use nullclear_scan_token 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": {
      "tokenAddress": "<tokenAddress>"
    },
    "name": "nullclear_audit_paid_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenAddressYes0x-prefixed Base Mainnet (chain 8453) ERC-20 token contract address0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

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 readOnly, idempotent, open-world and non-destructive, and the description adds genuinely new behavioral facts: a paid x402 flow with 10 free trial calls/day then $0.005 USDC, and that the return is a cryptographically signed receipt rather than a plain verdict. That cost/quota/attestation context goes well beyond what any annotation conveys.

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?

Two sentences, front-loaded with the paid-oracle purpose and pricing before the exclusivity caveat and the free alternative. Pricing appears in the first sentence and the routing rule in the second; nothing is redundant or padded.

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 a single well-described parameter and no output schema, the description still tells the agent what comes back (a signed EIP-712/keccak256 clearing receipt) and what it costs. Nothing needed to decide or invoke this tool correctly is missing.

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 single tokenAddress parameter is already documented as a 0x-prefixed Base Mainnet (8453) ERC-20 address. The description restates the same chain and token-type constraint but adds no format, validation, or edge-case detail beyond the schema, so the baseline of 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 ('Run NullClear's x402 Bazaar paid oracle') and pins the exact scope (Base Mainnet 8453, ERC-20 tokens) plus the distinctive output (a signed clearing receipt). It explicitly distinguishes itself from the sibling nullclear_scan_token, so an agent can separate the two 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 Guidelines5/5

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

It gives an explicit exclusive condition ('Use this ONLY when you specifically require a Base Bazaar EIP-712/keccak256 settlement receipt') and names the sibling to use otherwise, including that sibling's free quota. Both the when and the when-not, plus the alternative, are stated outright.

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