Is This Site Down?

Sites with stored history

list_monitored_sites

Read-onlyIdempotent

The 634 sites checked every 5 minutes, grouped in 17 categories. Without arguments returns the category list with counts; filter by category or a text query to get domains (at most 200 per call).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No	Case-insensitive substring of the domain or display name, e.g. "bank" or "google".
`category`	No	Category slug or name: social, streaming, ai, work, developer, shopping, finance, banks, gaming, telecom, government, education, messaging, news, travel, health, dating.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No
`sites`	No
`total`	Yes
`matched`	No
`category`	No
`returned`	No
`categories`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Without arguments: total + categories. With category or query: total, matched, returned, category, query, sites.",
+  "properties": {
+    "categories": {
+      "items": {
+        "properties": {
+          "count": {
+            "type": "integer"
+          },
+          "name": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "name",
+          "count",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "category": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "matched": {
+      "type": "integer"
+    },
+    "query": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "returned": {
+      "type": "integer"
+    },
+    "sites": {
+      "items": {
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "checkedFrom": {
+            "description": "sg = Singapore, us = Boston",
+            "enum": [
+              "sg",
+              "us"
+            ],
+            "type": "string"
+          },
+          "domain": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "statusUrl": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "domain",
+          "name",
+          "category",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total"
+  ],
+  "type": "object"
+}

First observedSep 12, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds valuable behavior beyond these: the 5-minute check interval, 17 predefined categories, the 200-result cap per call, and the mode-dependent output. It fully discloses what happens with and without arguments, with no contradiction to 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?

The description is two sentences long, front-loads the key facts (sites, frequency, categories), and wastes no words. Every clause contributes to understanding invocation behavior or output scope.

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?

Given that an output schema exists and annotations cover safety, the description covers the essential invocation modes, the pagination limit, and the grouping structure. An agent has enough information to call the tool correctly without needing additional explanation.

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%, so the baseline is 3. The description adds the semantic that filters produce domains and no-args produce categories, but it does not clarify whether query and category are mutually exclusive or combined. It provides marginal extra meaning beyond the schema, not enough to raise the score.

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 states a specific verb and resource: it lists the 634 monitored sites, details their check frequency, and explains the two output modes (category list or domain list). It clearly differentiates from siblings like check_site or site_history by focusing on the list of sites with stored history, so an agent can select it without opening schemas.

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?

The description gives clear usage context: without arguments returns categories with counts; filtering by category or query returns domains. It does not explicitly route to alternatives or state when not to use this tool, but the behavior is unambiguous enough for correct invocation.

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?