P0: email check, uptime, web reader

by dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank

URL uptime ping

url_uptime_ping

Read-onlyIdempotent

Use when you need to know if a URL is up right now (uptime ping, health check, link check): one HEAD request from a Cloudflare edge, up to 4 redirects; returns ok, status, latency_ms, tls. Returns the paid x402 request for your input (GET /v1/uptime/ping, $0.01 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For several URLs use url_uptime_ping_batch. With an access key (Authorization: Bearer p0k_..., buy at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/keys/buy?usd=5) the tool pays the call itself, returns the data and deducts the price.

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": "url_uptime_ping"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	public http or https URL to check, e.g. https://example.com/ (ports 80, 443, 8080, 8443)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations cover safety (readOnly, idempotent, non-destructive), but the description adds genuinely new behavior: a single HEAD request from a Cloudflare edge, follow up to 4 redirects, the returned fields, $0.01 pricing, and the guarantee that bad input is refused before any charge. It even documents the access-key payment flow and where to buy a key.

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?

Front-loaded with the trigger and behavior, then payment mechanics. It is dense and the long key-purchase URL adds bulk, but nearly every sentence carries operational information, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, the description covers what the call does, what it returns, the cost, the payment options, and failure handling. An agent has everything needed to decide and invoke correctly.

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% and the single url parameter is already documented with allowed ports, so the schema carries the parameter semantics. The description adds only the 'public http or https URL' framing, which is consistent but not substantial 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?

States a specific verb and resource ('uptime ping / health check' of a URL) and explicitly frames the output shape (ok, status, latency_ms, tls). It cleanly distinguishes itself from the sibling url_uptime_ping_batch by telling the agent to use that tool for multiple URLs.

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?

Opens with an explicit when-to-use trigger ('know if a URL is up right now') and names the alternative for multi-URL cases. It also spells out the two invocation paths (unpaid x402 request vs. access-key auto-pay), so the agent knows which route applies.

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

All P0: email check, uptime, web reader tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?