Skip to main content
Glama

NullClear Pre-Execution Firewall & Arbiter

nullclear_score_wallet

Read-onlyIdempotent

Profile a raw 0x EVM wallet address on Base Mainnet (8453) for OFAC sanctions exposure, on-chain counterparty wash-trade concentration, ETH/USDC balances, transaction count, and ERC-8004 ownership (10 free trials/day, then $0.005 USDC). Returns riskScore (0-100), riskLevel, and ERC-8004 registration status. Do NOT pass a numeric ERC-8004 agent ID here — use nullclear_check_reputation for numeric agentId trust audits.

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": {
      "walletAddress": "<walletAddress>"
    },
    "name": "nullclear_score_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainIdNoEVM chain ID (default 8453 for Base Mainnet)
walletAddressYes0x-prefixed 42-char EVM wallet address on Base Mainnet to screen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered; the description adds what annotations cannot — per-call pricing and a daily free quota. It also previews the return payload (riskScore 0-100, riskLevel, ERC-8004 registration status) in the absence of an output schema. It stops short of saying how non-Base chainId values are handled or whether billing is automatic, which keeps it from a 5.

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?

Two dense sentences plus a routing warning, with the purpose front-loaded before outputs, pricing, and the exclusion. The middle enumeration of risk dimensions is long but each item is informative; minor tightening is possible but nothing is clearly filler.

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?

With no output schema, the description usefully names the returned fields and the scoring scale, and it covers cost and rate limits for a paid, single-purpose screening tool. Residual gaps are edge-case behavior (non-Base chains, failure/billing behavior on error), which are minor for a 2-parameter read-only call.

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%, so both walletAddress and chainId are already documented, including the 0x/42-char format and the 8453 default. The description reinforces the address-vs-agent-ID distinction but adds no syntax, format, or constraint detail beyond what the schema states — 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?

Opens with a specific verb ("Profile") and a precisely scoped resource ("raw 0x EVM wallet address on Base Mainnet (8453)"), then enumerates the exact risk dimensions checked: OFAC exposure, wash-trade concentration, balances, tx count, ERC-8004 ownership. It also names the case it does NOT handle, so an agent can separate it from nullclear_check_reputation 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?

Contains an explicit exclusion plus the correct alternative: "Do NOT pass a numeric ERC-8004 agent ID here — use nullclear_check_reputation for numeric agentId trust audits." It also surfaces the commercial threshold (10 free trials/day, then $0.005 USDC), which is a practical condition for choosing whether to call it.

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.