Skip to main content
Glama

NullClear Pre-Execution Firewall & Arbiter

nullclear_audit_paid_token

Read-onlyIdempotent

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 (10/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. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, and the description still adds material context: a free tier of 10 trial calls/day, then a $0.005 USDC cost, the chain pinning to Base Mainnet 8453, and the fact that the response is a signed receipt rather than a plain scan result. Cost, rate limit, and output nature are exactly the behavioral facts an agent needs before invoking a paid endpoint.

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 what the tool does and its cost model, closing with the routing decision to the cheaper alternative. Every clause carries information; 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?

For a one-parameter tool with full annotation coverage and no output schema, the description covers purpose, pricing, chain scope, return artifact, and the sibling alternative. Nothing needed to select or invoke it 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?

There is a single parameter with 100% schema description coverage, so the schema already documents the 0x-prefixed Base Mainnet ERC-20 address requirement, and the description largely repeats that constraint. It does not mention the schema's default address or any normalization rules, so it adds little beyond the structured field — 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?

States a specific verb and resource: run the x402 Bazaar paid oracle for Base Mainnet (8453) ERC-20 tokens, returning a cryptographically signed clearing receipt. It explicitly distinguishes itself from the sibling nullclear_scan_token, so an agent can tell the two apart 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?

Gives an explicit constraint ('Use this ONLY when you specifically require a Base Bazaar EIP-712/keccak256 settlement receipt alongside token LP and bytecode verification') and names the alternative free tool for the more common multi-chain scanning case. Both the when-to-use and when-not-to-use conditions are spelled out.

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.