SolidPing

Official

Overview Schema Source Related Servers Discussions Admin

Get status page

get_status_page

Read-onlyIdempotent

Fetch a status page by UID or slug, with optional sections, resources, and incidents to monitor uptime and track issues.

Instructions

Get one status page by UID or slug and return it. with=sections embeds its sections and their resources. include adds lists next to the page fields: "sections" (section metadata, display order), "resources" (the resources of the section named by sectionIdentifier) and "incidents" (the customer-facing incident publications on the page, filtered by state and active). Use list_status_pages to browse every page, and manage_status_page_section / _resource / _incident to change them. Read-only: works with mcp:read tokens.

Input Schema

TableJSON Schema

Name	Required	Description
`with`	No	"sections" to include nested sections and their resources
`state`	No	With include=incidents: only publications in this public state. Allowed: "investigating", "identified", "monitoring", "resolved".
`active`	No	With include=incidents: when true, only publications that are not resolved.
`include`	No	Extra lists to return with the page. An unknown value is an error. Do not combine "sections" with with=sections.
`identifier`	Yes	Status page UID or URL-friendly slug, e.g. "public".
`sectionIdentifier`	No	Section UID or slug whose resources include=resources returns (required with it).

Output Schema

TableJSON Schema

Name	Required	Description
`uid`	Yes	Status page UID.
`name`	No	Display name.
`slug`	No	URL-friendly slug.
`enabled`	No	Whether the public page is served.
`sections`	No	Sections; absent unless with=sections (nested resources included) or include=sections (section metadata only) was passed.
`createdAt`	No	RFC3339 creation timestamp.
`incidents`	No	Incident publications on the page; present with include=incidents.
`isDefault`	No	Whether this is the organization's default page.
`resources`	No	Resources of the section named by sectionIdentifier; present with include=resources.
`visibility`	No	"public", "private" or "password".
`historyPeriod`	No	History window: "24h", "7d", "30d" or "90d".

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.38.5Oct 15, 2026

addedInput schema / properties / active

Added value: +{
+  "description": "With include=incidents: when true, only publications that are not resolved.",
+  "type": "boolean"
+}

addedInput schema / properties / include

Added value: +{
+  "description": "Extra lists to return with the page. An unknown value is an error. Do not combine \"sections\" with with=sections.",
+  "items": {
+    "enum": [
+      "sections",
+      "resources",
+      "incidents"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / sectionIdentifier

Added value: +{
+  "description": "Section UID or slug whose resources include=resources returns (required with it).",
+  "type": "string"
+}

addedInput schema / properties / state

Added value: +{
+  "description": "With include=incidents: only publications in this public state. Allowed: \"investigating\", \"identified\", \"monitoring\", \"resolved\".",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "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"
+    },
+    "incidents": {
+      "description": "Incident publications on the page; present with include=incidents.",
+      "items": {
+        "properties": {
+          "autoCreated": {
+            "description": "True when the publication was created by the auto-publish pipeline.",
+            "type": "boolean"
+          },
+          "createdAt": {
+            "description": "RFC3339 creation timestamp.",
+            "type": "string"
+          },
+          "humanTouched": {
+            "description": "True once an operator edited it, which stops auto-resolve.",
+            "type": "boolean"
+          },
+          "incidentUid": {
+            "description": "Linked internal incident UID, when the publication tracks one.",
+            "type": "string"
+          },
+          "publishedAt": {
+            "description": "RFC3339 timestamp when the entry appeared on the page.",
+            "type": "string"
+          },
+          "resolvedAt": {
+            "description": "RFC3339 timestamp when it was resolved; absent while open.",
+            "type": "string"
+          },
+          "severity": {
+            "description": "Public severity: minor, major or critical; absent when unset.",
+            "type": "string"
+          },
+          "stale": {
+            "description": "True when the linked incident has resolved while the entry is still open.",
+            "type": "boolean"
+          },
+          "state": {
+            "description": "Public state: investigating, identified, monitoring or resolved.",
+            "type": "string"
+          },
+          "statusPageUid": {
+            "description": "UID of the status page the publication lives on.",
+            "type": "string"
+          },
+          "title": {
+            "description": "Customer-facing title.",
+            "type": "string"
+          },
+          "uid": {
+            "description": "Publication UID.",
+            "type": "string"
+          },
+          "updatedAt": {
+            "description": "RFC3339 last-update timestamp.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "isDefault": {
+      "description": "Whether this is the organization's default page.",
+      "type": "boolean"
+    },
+    "name": {
+      "description": "Display name.",
+      "type": "string"
+    },
+    "resources": {
+      "description": "Resources of the section named by sectionIdentifier; present with include=resources.",
+      "items": {
+        "properties": {
+          "checkGroupUid": {
+            "description": "Pinned check group UID, when the resource targets a group.",
+            "type": "string"
+          },
+          "checkUid": {
+            "description": "Pinned check UID, when the resource targets a check.",
+            "type": "string"
+          },
+          "explanation": {
+            "description": "Short explanation rendered under the resource.",
+            "type": "string"
+          },
+          "position": {
+            "description": "Display position within the section (smaller renders earlier).",
+            "type": "integer"
+          },
+          "publicName": {
+            "description": "Display name shown on the public page.",
+            "type": "string"
+          },
+          "uid": {
+            "description": "Resource UID.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "sections": {
+      "description": "Sections; absent unless with=sections (nested resources included) or include=sections (section metadata only) was passed.",
+      "items": {
+        "properties": {
+          "name": {
+            "description": "Section display name.",
+            "type": "string"
+          },
+          "position": {
+            "description": "Display position (smaller renders earlier).",
+            "type": "integer"
+          },
+          "resources": {
+            "description": "Pinned checks and groups of the section.",
+            "items": {
+              "properties": {
+                "checkGroupUid": {
+                  "description": "Pinned check group UID, when the resource targets a group.",
+                  "type": "string"
+                },
+                "checkUid": {
+                  "description": "Pinned check UID, when the resource targets a check.",
+                  "type": "string"
+                },
+                "explanation": {
+                  "description": "Short explanation rendered under the resource.",
+                  "type": "string"
+                },
+                "position": {
+                  "description": "Display position within the section (smaller renders earlier).",
+                  "type": "integer"
+                },
+                "publicName": {
+                  "description": "Display name shown on the public page.",
+                  "type": "string"
+                },
+                "uid": {
+                  "description": "Resource UID.",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "selector": {
+            "description": "Dynamic membership rule; absent on hand-curated sections.",
+            "type": "object"
+          },
+          "slug": {
+            "description": "URL-friendly slug, unique within the page.",
+            "type": "string"
+          },
+          "uid": {
+            "description": "Section UID.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "slug": {
+      "description": "URL-friendly slug.",
+      "type": "string"
+    },
+    "uid": {
+      "description": "Status page UID.",
+      "type": "string"
+    },
+    "visibility": {
+      "description": "\"public\", \"private\" or \"password\".",
+      "type": "string"
+    }
+  },
+  "required": [
+    "uid"
+  ],
+  "type": "object"
+}

First observedv0.32.1Sep 26, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds genuinely new context: the mcp:read token requirement and the behavioral effect of each include value (sections embed their resources; incidents are filtered by state and active). It stops short of describing pagination or error behavior for a missing identifier.

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, then the modifier semantics, then sibling routing – a sensible order with no filler. The include parentheticals are dense, but each clause carries real information.

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?

For a 6-parameter read tool with an output schema present, the description covers the modifier interactions, filtering semantics, and auth scope, so nothing essential is missing. Return-value documentation is correctly delegated to the output schema.

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?

Schema description coverage is 100%, so the baseline is 3, but the description earns more by explaining what each include list actually returns (section metadata/display order, resources of sectionIdentifier, customer-facing incidents filtered by state and active) and by flagging the with=sections vs include=sections overlap.

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+resource (get one status page by UID or slug) and immediately distinguishes itself from siblings by naming list_status_pages for browsing and the manage_status_page_* tools for mutation. An agent can route correctly without opening any schema.

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?

Explicitly names the alternatives and the condition that selects them: browse with list_status_pages, change sections/resources/incidents with the manage_* tools. It also states the read-token scope, so the when-to-use picture is complete.

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