Skip to main content
Glama

Is this website up? Returns up/down, HTTP status, response time in ms, final URL

status
Read-only

Is this website up? Returns up/down, HTTP status, response time in ms, final URL and content type. Cheapest uptime check for agents. Fast (under 2 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.001 per call (x402, USDC on Base).

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint the description discloses real operational facts: under-2s latency, a 20-call/day free allowance shared across free tools, and a $0.001 per-call x402 path with no upfront payment. Left unstated is the critical failure behaviour — whether a non-200 or unreachable host yields a 'down' result or a tool error.

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 question and the return fields, then cost. Sentences are short and each carries information; the pricing sentence is longer than strictly needed but is material to tool selection rather than filler.

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 two-parameter read-only probe with no output schema, the description covers what it does, what it returns, how fast, and how it is billed — the full decision surface an agent needs. The mention of 'final URL' also signals redirect following, which is the main ambiguity such a tool has.

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 the url and payment parameters are already documented in structured form, and description adds little syntax detail. It does add policy context around when payment kicks in, which informs the payment parameter, but the mechanics (first call returns requirements, then sign) live in the schema, so baseline 3 applies.

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?

Names the specific check ('Is this website up?') and enumerates exactly what comes back: up/down, HTTP status, response time in ms, final URL, content type. That is enough for an agent to separate it from neighbours like https_check, redirects or broken_links, which probe related but different things.

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?

'Cheapest uptime check for agents' implies when to reach for it, and the price line pushes agents toward it for bulk/low-value checks. But no sibling is named, and there is no when-not guidance (e.g. use https_check for certificate/TLS detail, redirects for chain tracing) even though several siblings overlap.

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.