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

NullClear — Web3 Security & Tx Decoder

Official

nullclear_fetch_guarded

Read-onlyIdempotent

Fetch public HTTPS APIs via guarded GET/POST requests that block 5xx crashes, empty JSON, paywall traps, and refusal strings; returns a verified payload and receipt or voids settlement on failure.

Instructions

Execute a zero-schema Auto-Guarded HTTP GET/POST request through NullClear's firewall against HTTP 5xx crashes, empty JSON bodies, Cloudflare/soft-paywall traps, and LLM refusal strings (10 free trials/day, then $0.005 USDC via Bazaar). Returns verified payload and executionReceipt, or voids settlement on failure. Do NOT use for plain HTML docs-to-Markdown conversion (use nullclear_read_markdown) or when custom JSON Schema/invariants/failover are needed (use nullclear_execute_escrow).

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": {
      "url": "<url>"
    },
    "name": "nullclear_fetch_guarded"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTPS API or data endpoint URL to fetch with automatic crash, paywall, and refusal guards
bodyNoOptional serialized JSON request body string for POST requests
methodNoHTTP method ('GET' or 'POST', default 'GET')GET

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, open-world, non-destructive), the description discloses cost/quota mechanics, that a settlement is voided on failure, and that the return is a verified payload plus an executionReceipt. The one tension is that POST is offered while readOnlyHint=true declares no side effects; a POST to a remote API can mutate server state, and the description does not reconcile this. That is a gap in disclosure rather than a direct contradiction of the annotation text.

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: the first front-loads the capability and its guards plus pricing, the second carries the exclusion rules. It is dense but every clause carries routing or cost information; the only friction is unexplained jargon ('Bazaar', 'voids settlement') that adds slight parsing cost.

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 states what comes back (verified payload and executionReceipt) and what happens on failure (settlement voided), which is the key unknown for a paid call. What is still unstated is the observable behavior when a guard trips — error shape, whether the trial is consumed, or retry semantics — leaving a small hole for a paid, guarded fetch.

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%, so url, body, and method are already fully documented, including the GET/POST enum and the JSON-string requirement for body. The phrase 'zero-schema' adds a meaningful hint (no JSON Schema is supplied for the response), but the description contributes nothing about URL constraints, body serialization, or method-dependent behavior beyond the schema.

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 states a specific verb and resource: 'Execute a zero-schema Auto-Guarded HTTP GET/POST request through NullClear's firewall,' and enumerates the exact failure classes it defends against (5xx crashes, empty JSON bodies, Cloudflare/soft-paywall traps, LLM refusal strings). It also names the sibling tools it is not, so an agent can separate it from nullclear_read_markdown and nullclear_execute_escrow without opening any 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?

Explicit negative routing is given: do not use for HTML docs-to-Markdown (use nullclear_read_markdown) and do not use when custom JSON Schema/invariants/failover are required (use nullclear_execute_escrow). The free-trial quota and per-call price (10/day then $0.005 USDC) further tell the agent when this is the economical choice.

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