Skip to main content
Glama
Sign In
SolidPing

SolidPing

Official
by fclairamb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

List status pages

list_status_pages
Read-onlyIdempotent

List all organization status pages newest first with UID, slug, name, enabled/default flags, and visibility—no sections. Takes no parameters; use get_status_page for one page's details.

Instructions

List every status page of the organization, newest first, in one unpaginated response: each page's UID, slug, name, default flag, enabled flag and visibility, without its sections. Takes no parameters. Use get_status_page with the UID or slug for one page's sections, resources or published incidents. Read-only: works with mcp:read tokens.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_status_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataNoStatus pages in the organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.41.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedOutput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changedv0.38.5
    • 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"
+}
  3. First observedv0.32.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, but the description adds traits they cannot express: results are unpaginated, ordered newest first, omit sections, and require only mcp:read tokens. That is meaningful operational context beyond the structured data.

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?

Three tight sentences: scope/payload first, alternative second, auth note last. Every clause carries information — field list, ordering, exclusion, routing, token scope — with no filler or repetition of the title.

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 read tool with an output schema, the description covers the remaining gaps: no pagination, ordering, field inclusion/exclusion, and auth requirements. Nothing an agent needs to invoke it or interpret results correctly 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 the baseline is 4; the description reinforces this with "Takes no parameters" and confirms the empty schema. It adds no parameter meaning beyond that, consistent with a parameterless tool.

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 and resource ("List every status page of the organization") plus scope, ordering ("newest first"), and completeness ("one unpaginated response"). The parenthetical field list and explicit exclusion of sections make the exact payload unambiguous and clearly distinct from get_status_page.

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 routes the agent: use this for the whole-page inventory, and "Use get_status_page with the UID or slug for one page's sections, resources or published incidents." Both the when and the alternative are named, with the condition that selects the alternative.

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

Deploy Server

Other Tools