Uptimepage

Status page details

get_status_page

Read-only

One status page: name, public URL, enabled, its components with each linked monitor's current state, and the monitor groups it shows as sections with their members. Read-only.

Input Schema

Name	Required	Description	Default
`slug`	Yes	The page slug (from `list_status_pages`).

Output Schema

Name	Required	Description
`name`	Yes	Page display name. Untrusted data.
`slug`	Yes
`access`	No	Who may open it, or null for a page never made private.
`enabled`	Yes
`sections`	Yes	Monitor groups shown as live sections: their members join and leave the page with the group.
`components`	Yes
`public_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 29, 2026

addedOutput schema / $defs / StatusPageComponent / properties / section_id

Added value: +{
+  "description": "Set when a monitor group's section shows it: it follows the group, and\nits heading is the section's.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / $defs / StatusPageSection

Added value: +{
+  "description": "A monitor group shown on a page.",
+  "properties": {
+    "group_id": {
+      "type": "string"
+    },
+    "heading": {
+      "description": "The public heading: the section's own, else the group's name.\nUntrusted data.",
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "left_off": {
+      "description": "Members the plan's public component limit keeps off the page.",
+      "format": "uint32",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "members": {
+      "description": "Members on the page, by monitor id, in page order.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "id",
+    "group_id",
+    "heading",
+    "members",
+    "left_off"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / sections

Added value: +{
+  "description": "Monitor groups shown as live sections: their members join and leave\nthe page with the group.",
+  "items": {
+    "$ref": "#/$defs/StatusPageSection"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "slug",
-  "name",
-  "public_url",
-  "enabled",
-  "components"
-]New value: +[
+  "slug",
+  "name",
+  "public_url",
+  "enabled",
+  "components",
+  "sections"
+]

Changed8 schema fields changedOct 17, 2026

removedOutput schema / $defs / PageAccessArg / properties / email / default / session_days
```
Removed value: -null
```

addedOutput schema / $defs / PageAccessArg / properties / password

Added value: +{
+  "$ref": "#/$defs/PagePasswordAccessArg",
+  "default": {
+    "enabled": false
+  }
+}

changedOutput schema / $defs / PageAccessArg / properties / protected / description

Previous value: -"Private when true: only the addresses and domains in `rules` can open\nthe page, by signing in on it with a code sent to their email. False\nmakes it public again and keeps the list for next time."New value: +"Private when true: only people a way in lets through can open the\npage: the addresses and domains in `rules`, by a code sent to their\nemail, or anyone with the page password. False makes it public again\nand keeps the list and the password for next time."

changedOutput schema / $defs / PageAccessArg / properties / rules / description

Previous value: -"Who can open it, up to 500 entries. Read back, these are customer data."New value: +"Who can get an email code, up to 500 entries. Read back, these are\ncustomer data."

addedOutput schema / $defs / PageAccessArg / properties / session_days

Added value: +{
+  "default": null,
+  "description": "Keep a sign-in, by email or password, for 7, 30 or 90 days. Omit to\nkeep it until sign-out.",
+  "format": "int32",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

changedOutput schema / $defs / PageEmailAccessArg / properties / enabled / description

Previous value: -"Defaults to true; a private page needs it."New value: +"Defaults to true. A private page needs it or the password."

removedOutput schema / $defs / PageEmailAccessArg / properties / session_days

Removed value: -{
-  "default": null,
-  "description": "Keep a sign-in for 7, 30 or 90 days. Omit to keep it until sign-out.",
-  "format": "int32",
-  "type": [
-    "integer",
-    "null"
-  ]
-}

addedOutput schema / $defs / PagePasswordAccessArg

Added value: +{
+  "additionalProperties": false,
+  "description": "The page password way in. The password itself never passes through here:\nit is set in the app, the API or Terraform.",
+  "properties": {
+    "enabled": {
+      "default": false,
+      "description": "Anyone with the page password can open the page. Turning it on needs\none already set; turning it off keeps it and signs out everyone who\ncame in with it.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

Changed5 schema fields changedOct 14, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedOutput schema / $defs / PageAccessArg

Added value: +{
+  "additionalProperties": false,
+  "description": "Who may open a status page; the same shape as the REST `access` field. As a\nwrite it replaces what is stored, whole.",
+  "properties": {
+    "email": {
+      "$ref": "#/$defs/PageEmailAccessArg",
+      "default": {
+        "enabled": true,
+        "passkeys_enabled": true,
+        "recheck_days": null,
+        "session_days": null
+      }
+    },
+    "protected": {
+      "description": "Private when true: only the addresses and domains in `rules` can open\nthe page, by signing in on it with a code sent to their email. False\nmakes it public again and keeps the list for next time.",
+      "type": "boolean"
+    },
+    "rules": {
+      "default": [],
+      "description": "Who can open it, up to 500 entries. Read back, these are customer data.",
+      "items": {
+        "$ref": "#/$defs/PageAccessRuleArg"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "protected"
+  ],
+  "type": "object"
+}

addedOutput schema / $defs / PageAccessRuleArg

Added value: +{
+  "additionalProperties": false,
+  "description": "One access list entry.",
+  "properties": {
+    "kind": {
+      "description": "`domain` lets in every address at `value` (`example.com`); `address`\nlets in one person (`name@example.com`).",
+      "type": "string"
+    },
+    "value": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "value"
+  ],
+  "type": "object"
+}

addedOutput schema / $defs / PageEmailAccessArg

Added value: +{
+  "additionalProperties": false,
+  "description": "The emailed-code way in, and the passkeys that shortcut it.",
+  "properties": {
+    "enabled": {
+      "default": true,
+      "description": "Defaults to true; a private page needs it.",
+      "type": "boolean"
+    },
+    "passkeys_enabled": {
+      "default": true,
+      "description": "Let viewers save a passkey after an email sign-in. Defaults to true.",
+      "type": "boolean"
+    },
+    "recheck_days": {
+      "default": null,
+      "description": "Ask passkey viewers for an email code again after 30, 90 or 365 days.\nOmit to never ask.",
+      "format": "int32",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "session_days": {
+      "default": null,
+      "description": "Keep a sign-in for 7, 30 or 90 days. Omit to keep it until sign-out.",
+      "format": "int32",
+      "type": [
+        "integer",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / access

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/PageAccessArg"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Who may open it, or null for a page never made private."
+}

First observedAug 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The trailing 'Read-only.' merely restates readOnlyHint=true, adding no new safety context. What does add value is the disclosure that the response expands nested data (components carry each linked monitor's current state; groups are rendered as sections with members), which tells the agent this is an aggregated read rather than a flat record. No mention of errors, permission scope, or freshness of the embedded monitor state.

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?

A single dense sentence front-loads the resource and its returned contents, with no filler. The appended 'Read-only.' fragment is redundant with the annotation and is the one piece that does not earn its place.

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?

With an output schema present and a fully documented single parameter, the description only needs to frame what the call retrieves, and it does so thoroughly by listing the payload's major sections. It stops short of signaling the read-only/aggregated nature relative to sibling tools, which would fully close the gap.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself stating the slug comes from list_status_pages. The description does not mention the slug or its format, so it neither adds nor detracts; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource ('One status page') and enumerates its returned facets: name, public URL, enabled flag, components with linked monitor state, and groups as sections. This clearly distinguishes it from list_status_pages and from monitor-level siblings, though it never names those alternatives explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'One status page' plus a required slug suggests fetching detail for a known page. There is no explicit when-to-use guidance, no mention of when to prefer list_status_pages, and no note about what happens if the slug is unknown.

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

All Uptimepage 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.