SolidPing

Official

Overview Schema Source Related Servers Discussions Admin

Create status page

create_status_page

Create a status page for an organization and return it. Reject duplicate slugs, set one default, and seed a Services section.

Instructions

Create a new status page for the organization and return the created page. A duplicate slug is rejected with a conflict, never merged. Only one page can be the default: the first page always becomes it, and isDefault:true demotes the previous default. Every new page is seeded with a default "Services" section and starts enabled and public — use manage_status_page_section to add more sections and update_status_page to edit the page later. Requires the mcp scope (mcp:read tokens are refused) and at least the user role in the organization.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Status page display name (required), e.g. "Public status".
`slug`	Yes	URL-friendly slug (required, unique per org), e.g. "public".
`language`	No	Language code, e.g. "en" or "fr".
`customCss`	No	Custom CSS injected into the public page as a <style> element. Overrides the theme's CSS custom properties (--brand, --background, --foreground, --card, --border, the status colors, and the .dark variant). Max 64 KB; @import is rejected.
`isDefault`	No	Whether this is the org's default status page (only one allowed).
`visibility`	No	Visibility setting. Allowed: "public", "private". Default "public".
`autoPublish`	No	Automatically publish incidents affecting this page's resources as public incidents. New pages default to true; pages that existed before this feature shipped default to false.
`autoResolve`	No	What an auto-created publication does when its incident resolves. Allowed: "always", "if_untouched" (default — a publication a human has edited is left for them to close), "never".
`description`	No	Optional free-text description shown in the UI.
`historyDays`	No	Days of history to show on the page (default 90).
`showAvailability`	No	Display availability percentage on the public page.
`showResponseTime`	No	Display response-time charts on the public page.
`autoPublishDelaySeconds`	No	Debounce in seconds before an incident becomes public (default 60). 0 publishes immediately. An incident that resolves inside the delay is never published at all.

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.
`createdAt`	No	RFC3339 creation timestamp.
`isDefault`	No	Whether this is the organization's default page.
`visibility`	No	"public", "private" or "password".
`historyPeriod`	No	History window: "24h", "7d", "30d" or "90d".

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.38.5Oct 15, 2026

changedInput schema / properties / visibility / description

Previous value: -"Visibility setting. Allowed: \"public\", \"private\". Default depends on system config."New value: +"Visibility setting. Allowed: \"public\", \"private\". Default \"public\"."

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"
+    },
+    "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"
+    }
+  },
+  "required": [
+    "uid"
+  ],
+  "type": "object"
+}

First observedv0.32.1Sep 26, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing concrete side effects and constraints: duplicate slugs are rejected with a conflict rather than merged, the first page auto-becomes default and isDefault:true demotes the previous default, every page is seeded with a Services section and starts enabled/public, and it requires the mcp scope (mcp:read refused) plus user role.

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?

Four dense sentences, front-loaded with the core action and conflict behavior before the follow-up routing and auth requirements. No filler, though the auth sentence is somewhat appended rather than integrated.

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?

An output schema already exists so return-value description is not needed, and the description covers the remaining gaps an agent would care about: conflict handling, default-page side effects, seeding, initial state, and authorization requirements.

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 schema already documents all 13 parameters in detail, establishing a baseline of 3. The description adds only marginal parameter meaning (isDefault demotion semantics, default-enabled/public state) beyond what the schema and annotations already carry.

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?

Specific verb+resource ('Create a new status page for the organization') with the return value named, and it distinguishes itself from siblings by pointing to manage_status_page_section and update_status_page for the follow-up operations it does not cover.

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 routes the agent to update_status_page and manage_status_page_section for later edits and section management, and the duplicate-slug rule implies this tool is only for first-time creation. There is no explicit 'do not use if the page already exists' exclusion, keeping it short of a 5.

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