Skip to main content
Glama

NullClear Pre-Execution Firewall & Arbiter

nullclear_discover_apis

Read-onlyIdempotent

Search NullClear's audited x402 and ERC-8004 endpoint directory by keyword, category, minimum uptime, and maximum latency. Use this before paying external x402 sellers to find reliable APIs and retrieve their NullClear Zero-Loss Proxy URL (https://api.nullclear.dev/https://...). Returns matched endpoints with priceAtomic, uptimeScore, latencyMs, and proxy URL. Do NOT use to execute a call (pass the returned URL to nullclear_execute_escrow).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nullclear_discover_apis"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoKeyword filter matching endpoint URL or description (e.g. 'oracle', 'security', 'token', 'wallet')
categoryNoExact category filter ('oracle', 'security', 'data', or 'ai')
minUptimeNoMinimum rolling uptime percentage threshold from 0 to 100 (default 95)
maxLatencyMsNoMaximum acceptable edge round-trip latency in milliseconds (default 2000)
verifiedOnlyNoWhen true, filter exclusively to canary-verified HTTP 402 endpoints (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and the description adds real context on top: the results are audited/canary-verified, and each match carries priceAtomic, uptimeScore, latencyMs and a Zero-Loss proxy URL with a concrete URL template. It does not mention result-count limits, pagination, or rate-limiting on the open-world directory, which is the remaining behavioral gap.

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?

Three sentences, front-loaded with purpose and filters, then the return shape, then the exclusion. Every clause carries information and nothing is repeated across sentences.

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 compensates by naming the returned fields and the proxy URL format, and it handles the sibling handoff for a zero-required-parameter search tool. The only omission is result-set size/pagination behavior, which matters for an open-world directory search but is minor here.

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 the schema already explains every parameter including defaults and example keywords. The description only restates the filter axes (keyword, category, minimum uptime, maximum latency) without adding semantics such as how uptime is windowed or latency is measured, so it stays at the baseline.

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 ('Search NullClear's audited x402 and ERC-8004 endpoint directory') plus the filter dimensions, and names the outcome the agent gets (matched endpoints with proxy URL). It also explicitly distinguishes itself from the execution sibling by saying the returned URL must be passed to nullclear_execute_escrow.

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 a clear positive trigger ('Use this before paying external x402 sellers to find reliable APIs') and an explicit exclusion ('Do NOT use to execute a call'), naming the correct alternative and the handoff mechanic. Nothing about when to select this versus the escrow tool is left to inference.

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.