Skip to main content
Glama

Check whether URLs are up, with status and response time

uptime
Read-only

Checks up to five public URLs now from this Worker: up or down, HTTP status, the final URL after up to five redirects, response time in milliseconds, whether TLS was used, content type and length, and the Cloudflare data centre (colo) the check ran from. A down site is a valid 200 answer with up false and the error, not a failure. The check is one GET per hop, so it measures the first response, not the full page. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "urls": "<urls>"
    },
    "name": "uptime"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesComma-separated public http or https URLs, 1 to 5

Output Schema

NameRequiredDescriptionDefault
coloNo
countNo
checksNo
sourceNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only declare readOnly and openWorld; the description adds substantial behavior the agent could not otherwise know: a down site returns a valid 200 with up=false rather than an error, the metric is the first response per hop rather than full page load, and up to five redirects are followed. It also discloses cost ($0.002 per successful call), the payment rail (x402 with USDC), and that failed calls are free.

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 core action and scope, and nearly every clause carries information (return fields, the down-site semantics, the measurement caveat, the price). The long comma-chained first sentence is dense but not padded.

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?

An output schema exists, so return-value detail is not strictly required, yet the description still covers the risky edge cases (down = 200 with up=false) and the cost model, which are the things an agent most needs before calling. The only material omission is guidance on when a different tool would be more appropriate.

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?

With one parameter and 100% schema coverage, the schema already documents 'Comma-separated public http or https URLs, 1 to 5'. The description restates the five-URL cap and public/http(s) constraint without adding format or encoding detail beyond it, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Checks up to five public URLs now from this Worker') and enumerates exactly what it returns: up/down, HTTP status, final URL, response time, TLS, content type/length, and colo. It is unambiguous about scope, though it never contrasts itself with related siblings such as redirects or certs, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the scope statement ('checks up to five public URLs now') and by the pricing line, which signals a paid per-call availability check. There is no explicit when-to-use/when-not guidance and no named alternative tool for adjacent tasks like following redirects or inspecting certificates.

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.

Resources