Skip to main content
Glama

YRUZ Uptime Check (0.003 USDC)

uptime_check
Read-onlyIdempotent

Is it up, right now, from the internet: HTTP status, final URL after redirects, DNS, connect, TLS and time-to-first-byte timings, HTTP version, response size, content type, server, TLS certificate days left, and an optional keyword that must appear on the page. For monitors, deploy checks and agents that must not act on a dead site. Price: 0.003 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"uptime_check"}. Same tool over HTTP: https://yruz.one/api/uptime?url=https%3A%2F%2Fyruz.one%2F

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

Input Schema

NameRequiredDescriptionDefault
urlYesURL or domain (required)
keywordNooptional text that must appear in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / url / examples
      Added value: +[
      +  "https://yruz.one/"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, but the description adds substantial non-obvious behavior: price (0.003 USDC), x402 payment with USDC on Base or Solana with no account/API key, invalid input refused before payment, failed runs never charged, and a PaymentRequired response if unpaid. It also provides an alternative HTTP invocation path.

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?

The capability statement is front-loaded and the return-value enumeration earns its length because there is no output schema. Pricing, payment mechanics, the get_example pointer and the HTTP URL are all distinct actionable facts, though the density of the first sentence is high and slightly hurts scannability.

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?

With no output schema, the description correctly compensates by enumerating returned fields, and it covers the payment/auth model, the failure semantics, and how to discover a call example. An agent has everything needed to invoke it and interpret a refusal.

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 both parameters are already documented. The description adds only marginal nuance — clarifying that the keyword must appear 'on the page' rather than just 'in the response', and implying the url may be a bare domain — which justifies the baseline 3 rather than more.

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 opens with a specific verb+resource+scope ('Is it up, right now, from the internet') and then enumerates exactly what is measured: HTTP status, redirect chain, DNS/connect/TLS/TTFB timings, TLS days left, and keyword presence. This makes it trivially distinguishable from siblings like url_safety_check, broken_links, site_audit or x402_endpoint_check 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit use case — 'For monitors, deploy checks and agents that must not act on a dead site' — which tells an agent when this tool is the right pick. It stops short of naming alternative siblings or stating when NOT to use it (e.g. for safety/blacklist checks use url_safety_check), so it is clear but not fully routing.

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.