Is This Site Down?

Uptime and recent incidents of a monitored site

site_history

Read-onlyIdempotent

Uptime percentage over 24 h and over the requested window (up to 7 days), the list of outages in that window, when the site was last seen down, the current state and user-report counts. Only for monitored sites (see list_monitored_sites); use check_site for anything else.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	Window in days (1–7, default 7).
`domain`	Yes	A monitored domain, e.g. "github.com".

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes
`days`	Yes
`name`	Yes
`domain`	Yes
`current`	Yes
`category`	Yes
`lastDown`	Yes
`incidents`	Yes
`statusUrl`	Yes
`uptime24h`	Yes	Percent, null if no data yet
`reports24h`	Yes
`checkedFrom`	Yes	sg = Singapore, us = Boston
`uptimeWindow`	Yes	Percent over `days`, null if no data yet
`reportsLastHour`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "category": {
+      "type": "string"
+    },
+    "checkedFrom": {
+      "description": "sg = Singapore, us = Boston",
+      "enum": [
+        "sg",
+        "us"
+      ],
+      "type": "string"
+    },
+    "current": {
+      "properties": {
+        "checkedAt": {
+          "description": "ISO 8601",
+          "type": "string"
+        },
+        "domain": {
+          "type": "string"
+        },
+        "finalUrl": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "ip": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "latencyMs": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "reason": {
+          "type": "string"
+        },
+        "redirected": {
+          "type": "boolean"
+        },
+        "scheme": {
+          "enum": [
+            "https",
+            "http",
+            null
+          ],
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "server": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "state": {
+          "enum": [
+            "up",
+            "slow",
+            "error",
+            "maintenance",
+            "down"
+          ],
+          "type": "string"
+        },
+        "status": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "tls": {
+          "properties": {
+            "daysRemaining": {
+              "type": "number"
+            },
+            "issuer": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "validTo": {
+              "type": "string"
+            }
+          },
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "up": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "domain",
+        "up",
+        "state",
+        "status",
+        "latencyMs",
+        "checkedAt",
+        "reason"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "days": {
+      "type": "integer"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "incidents": {
+      "items": {
+        "properties": {
+          "durationMinutes": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "end": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "ongoing": {
+            "type": "boolean"
+          },
+          "start": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "start",
+          "end",
+          "durationMinutes",
+          "ongoing"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "lastDown": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "type": "string"
+    },
+    "reports24h": {
+      "type": "integer"
+    },
+    "reportsLastHour": {
+      "type": "integer"
+    },
+    "statusUrl": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "uptime24h": {
+      "description": "Percent, null if no data yet",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "uptimeWindow": {
+      "description": "Percent over `days`, null if no data yet",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "domain",
+    "name",
+    "category",
+    "checkedFrom",
+    "days",
+    "uptime24h",
+    "uptimeWindow",
+    "current",
+    "incidents",
+    "lastDown",
+    "reportsLastHour",
+    "reports24h",
+    "statusUrl",
+    "url"
+  ],
+  "type": "object"
+}

First observedSep 12, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the description need not restate safety. It adds useful context about the monitored-site restriction and the specific time windows and data returned, which helps an agent predict behavior without contradicting the annotations.

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?

Two sentences, no filler. The first sentence enumerates visible outputs and constraints; the second gives direct sibling routing. Every phrase earns its place.

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 low-complexity read-only tool with a complete input schemaebb and an output schema, the description is fully sufficient. It covers scope, usage boundaries, and alternatives, leaving no critical gap for an agent to call the tool 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 description coverage is 100%, with detailed descriptions for both domain and days. The description merely restates the 7-day window and adds the monitored-site constraint, providing no new parameter-level meaning beyond what the schema already covers.

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 clearly states the tool's data outputs: uptime percentages, outages, last-down time, current state, and user-report counts for a site. It also differentiates itself from siblings by explicitly limiting use to monitored sites and pointing to check_site for all other cases.

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?

The description gives explicit when-to-use guidance: only for monitored sites, referencing list_monitored_sites, and directs agents to use check_site for anything else. This directly answers the selection question and prevents misuse.

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

All Is This Site Down? 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?