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

NullClear — Web3 Security & Tx Decoder

Official

nullclear_execute_escrow

Execute paid x402 API calls through non-custodial escrow that settles only after schema and value checks pass, voiding payment if validation fails.

Instructions

Execute a paid x402 API request protected by NullClear deferred non-custodial EIP-3009 escrow, custom JSON Schema/value invariants, multi-seller failover routing, and outbound spend caps (10 free trials/day, then requires configured wallet key). Settles upstream payment ONLY when all schema, numeric, staleness, and refusal checks pass; otherwise voids authorization ($0 lost). Use this instead of nullclear_fetch_guarded whenever calling third-party x402 paid APIs with strict output contracts or fallback sellers.

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": {
      "targetUrl": "<targetUrl>"
    },
    "name": "nullclear_execute_escrow"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNoHTTP method for upstream callGET
fallbacksNoUp to 3 ordered backup seller objects ({ targetUrl, sellerAgentId, paymentSignatureHeader }) for automatic failover
targetUrlYesPrimary upstream HTTPS endpoint demanding HTTP 402 payment
invariantsNoField-level semantic invariants (numeric bounds, regex, forbidden substrings, timestamp freshness)
jsonSchemaNoJSON Schema Draft-07 object that upstream JSON must strictly satisfy
spendPolicyNoOutbound spend firewall caps ({ maxPerCallAtomic, maxDailyWalletAtomic })
minTrustScoreNoMinimum seller trust score (0-100, default 50)
sellerAgentIdNoERC-8004 seller agent ID for pre-flight trust and Sybil gating
rejectRefusalsNoVoid settlement if response contains canonical LLM refusal strings (default true)
requiredFieldsNoDot-notation field paths that must exist in upstream JSON (e.g. ['data.price'])
buyerPrivateKeyNoOptional buyer 0x private key overriding default Sponsored Free Trial or NULLCLEAR_PRIVATE_KEY

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare the generic profile (write, open-world, non-idempotent, non-destructive); the description adds the economically important behavior: settlement is conditional on schema/numeric/staleness/refusal checks, and failure voids the authorization at $0 loss. That conditional-settlement and zero-cost-on-failure contract is not derivable from any structured field and directly affects whether an agent should risk the call.

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?

Three sentences with a clear front-load: capability, then settlement semantics, then sibling routing. The first sentence is a dense comma-separated feature stack of protocol jargon ('EIP-3009', 'ERC-8004' implicitly) that costs readability, though each clause does carry real information rather than 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?

For an 11-parameter, deeply nested, no-output-schema tool, the description covers the parts an agent cannot infer: conditional settlement, void-on-failure, trial limits, and failover intent. It does not describe the response shape on success or how partial failover attempts are reported, which is the main remaining gap.

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 every parameter including nested `invariants`, `fallbacks`, and `spendPolicy` sub-fields is already documented, which sets the baseline at 3. The description corroborates the schema's themes (invariants, failover, spend caps) and links the trial cap to `buyerPrivateKey`, but adds no format, ordering, or precedence detail beyond what the schema provides.

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 concrete verb+resource ('Execute a paid x402 API request') and immediately scopes it with the distinctive mechanism (deferred non-custodial EIP-3009 escrow). It explicitly contrasts with the sibling `nullclear_fetch_guarded`, so an agent can distinguish 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?

States an explicit selection rule: use this instead of nullclear_fetch_guarded 'whenever calling third-party x402 paid APIs with strict output contracts or fallback sellers,' which implicitly routes plain paid fetches elsewhere. It also surfaces the operational precondition (10 free trials/day, then a configured wallet key), which is exactly the kind of gating an agent must check before calling.

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