Skip to main content
Glama
fettlesh

fettle-mcp

by fettlesh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Get a status page

get_status_page
Read-onlyIdempotent

Read a status page and its components to retrieve component IDs for creating status page incidents. Use the page UUID from the status page list.

Instructions

Read one status page with its components. It has the list_status_pages fields, where each component has id, monitor_id, display_name and position. Use it to get the component ids that create_status_page_incident takes as component_ids. To find a page use list_status_pages; for the incidents posted on it use list_status_page_incidents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesThe status page's uuid from list_status_pages. An id that is not a status page of this organization is a 404.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameYes
slugYes
groupsYes
created_atYes
descriptionYes
history_daysYes
is_publishedYes
ungrouped_componentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.1
    • addedInput schema / properties / page_id / description
      Added value: +"The status page's uuid from list_status_pages. An id that is not a status page of this organization is a 404."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "created_at": {
+      "type": "string"
+    },
+    "description": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "groups": {
+      "items": {
+        "properties": {
+          "components": {
+            "items": {
+              "properties": {
+                "display_name": {
+                  "anyOf": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                },
+                "id": {
+                  "format": "uuid",
+                  "type": "string"
+                },
+                "monitor_id": {
+                  "format": "uuid",
+                  "type": "string"
+                },
+                "position": {
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "id",
+                "monitor_id",
+                "display_name",
+                "position"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "id": {
+            "format": "uuid",
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "position": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "position",
+          "components"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "history_days": {
+      "type": "integer"
+    },
+    "id": {
+      "format": "uuid",
+      "type": "string"
+    },
+    "is_published": {
+      "type": "boolean"
+    },
+    "name": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "ungrouped_components": {
+      "items": {
+        "properties": {
+          "display_name": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "id": {
+            "format": "uuid",
+            "type": "string"
+          },
+          "monitor_id": {
+            "format": "uuid",
+            "type": "string"
+          },
+          "position": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "id",
+          "monitor_id",
+          "display_name",
+          "position"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "id",
+    "slug",
+    "name",
+    "description",
+    "is_published",
+    "history_days",
+    "created_at",
+    "groups",
+    "ungrouped_components"
+  ],
+  "type": "object"
+}
  2. First observedv0.5.4

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds value beyond that by disclosing the shape of the returned components (id, monitor_id, display_name, position) and the downstream consumer of the ids, which annotations cannot convey.

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 routing guidance, with no filler sentences. The middle sentence describing component fields is slightly dense but earns its place by telling the agent what it will get back for the component_ids use case.

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?

With an output schema present, the return values need not be re-explained, yet the description still summarizes component fields relevant to the chained call. Combined with a fully documented parameter and read-only annotations, nothing an agent needs to invoke this correctly is missing.

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 coverage is 100% and the single parameter's description already states the UUID source (list_status_pages) and the 404 for foreign ids. The description adds essentially no syntax or format detail beyond the schema, so the baseline 3 for a fully documented single parameter is appropriate.

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 ('Read one status page with its components') and immediately differentiates it from the closely related list_status_pages and list_status_page_incidents. An agent can distinguish this from every sibling without opening a 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 alternative for discovery ('To find a page use list_status_pages'), the alternative for the related sub-resource ('for the incidents posted on it use list_status_page_incidents'), and states a concrete downstream use case (feeding component_ids into create_status_page_incident). When-to-use is fully spelled out.

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