Skip to main content
Glama

NullClear Pre-Execution Firewall & Arbiter

nullclear_execute_escrow

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

The annotations declare a non-read-only, non-destructive, open-world, non-idempotent operation, so safety is already partially framed. The description adds meaningful behavior beyond that: settlement happens ONLY if all checks pass and otherwise the authorization is voided with $0 lost, which is exactly the risk model an agent needs. It does not, however, describe the response shape or what an error/void looks like to the caller.

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 sentences, front-loaded with the action and immediately followed by the settlement gating rule and the sibling alternative; nothing is padding. The first sentence is a dense pile of jargon clauses that takes effort to parse, which keeps it from a 5.

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 a complex 10-parameter escrow tool with nested objects and no output schema, the description covers the critical mechanics: gating conditions, failover, spend caps, and free-trial/auth limits. What remains thin is the return/error surface, which matters more here because no output schema exists to document it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description earns an upgrade by explaining the purpose of the structured inputs — invariants, schema, and staleness checks gate settlement, failover is multi-seller routing, and spendPolicy is an outbound firewall. This tells the agent what those objects are for, not just their shape, though it does not add per-parameter format detail.

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 (execute) and resource (a paid x402 API request) and then enumerates the concrete machinery involved: deferred non-custodial EIP-3009 escrow, JSON Schema/value invariants, multi-seller failover, and spend caps. It also distinguishes itself from nullclear_fetch_guarded by name, so an agent can tell the two apart without opening a 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?

It gives an explicit routing rule: use this instead of nullclear_fetch_guarded whenever calling third-party x402 paid APIs with strict output contracts or fallback sellers. It also states a prerequisite (10 free trials/day, then a configured wallet key is required). The only gap is that the 'when not' case is implied rather than stated for plain, contract-free fetches.

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.