SolidPing

Official

Overview Schema Source Related Servers Discussions Admin

List status pages

list_status_pages

Read-onlyIdempotent

List all status pages in your organization, sorted newest first, to quickly see all pages. Read-only and works with mcp:read tokens.

Instructions

List every status page in the organization, newest first, and return {data: [...]}. Use get_status_page for a single page by UID or slug (with=sections or include=sections for its contents). Read-only: works with mcp:read tokens.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	Status pages in the organization.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.38.5Oct 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Status pages in the organization.",
+      "items": {
+        "properties": {
+          "createdAt": {
+            "description": "RFC3339 creation timestamp.",
+            "type": "string"
+          },
+          "enabled": {
+            "description": "Whether the public page is served.",
+            "type": "boolean"
+          },
+          "historyPeriod": {
+            "description": "History window: \"24h\", \"7d\", \"30d\" or \"90d\".",
+            "type": "string"
+          },
+          "isDefault": {
+            "description": "Whether this is the organization's default page.",
+            "type": "boolean"
+          },
+          "name": {
+            "description": "Display name.",
+            "type": "string"
+          },
+          "slug": {
+            "description": "URL-friendly slug.",
+            "type": "string"
+          },
+          "uid": {
+            "description": "Status page UID.",
+            "type": "string"
+          },
+          "visibility": {
+            "description": "\"public\", \"private\" or \"password\".",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedv0.32.1Sep 26, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, but the description adds crucial auth context: 'works with mcp:read tokens'. Also specifies ordering (newest first) and response shape {data: [...]}, going beyond what annotations provide.

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 tight sentences, front-loaded with purpose and return shape, second sentence routes to alternative. No 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 parameterless list tool with an output schema, the description provides ordering, return structure, auth scope, and sibling routing. Nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so baseline is 4. The description mentions that get_status_page accepts include/sections parameters, which implies this tool does not; this is useful but not a parameter explanation for this tool itself.

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?

States a specific verb (List) and resource (status pages) with scope (in the organization) and ordering (newest first). Distinguishes from sibling get_status_page by contrast. An agent can identify the correct tool immediately.

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?

Explicitly names get_status_page as the alternative for a single page and hints that include/sections parameters are for that tool. No exclusions or edge cases like empty results, but the routing is clear and actionable.

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