Skip to main content
Glama
Sign In

Phare

by io.phare.mcp
OverviewDiscussionsAdmin

Get a status page current status

get_status_page_current_status
Read-onlyIdempotent

Get what a status page shows right now: the impact of its active incidents or maintenance, its availability over its timeframe, the status of each component and its published active incidents.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "status_page_id": "<status_page_id>"
    },
    "name": "get_status_page_current_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesID of the project to act on, see whoami
status_page_idYesID of the status page to show the current status for

Output Schema

NameRequiredDescriptionDefault
componentsNoComponents of the status page and their current status
updated_atNoDate of the data calculation
availabilityNoAverage availability of all associated monitors over the status page timeframe (30, 60 or 90 days), in percents
active_incidentsNoActive incidents linked to the status page, unpublished incidents are excluded
current_incident_impactNoHighest impact of all the active incidents linked to the status page, `maintenance` if there is no active incident and a maintenance window linked to the status page is in progress

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "active_incidents": {
+      "description": "Active incidents linked to the status page, unpublished incidents are excluded",
+      "items": {
+        "anyOf": [
+          {
+            "properties": {
+              "exclude_from_downtime": {
+                "description": "Flag to exclude the incident from downtime calculations",
+                "examples": [
+                  false
+                ],
+                "type": "boolean"
+              },
+              "id": {
+                "examples": [
+                  1
+                ],
+                "type": "integer"
+              },
+              "impact": {
+                "description": "Incident impact level",
+                "enum": [
+                  "unknown",
+                  "operational",
+                  "maintenance",
+                  "degraded_performance",
+                  "partial_outage",
+                  "major_outage"
+                ],
+                "type": "string"
+              },
+              "incident_at": {
+                "description": "Date of incident confirmation",
+                "format": "date-time",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "recovery_at": {
+                "description": "Date of incident recovery",
+                "format": "date-time",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "state": {
+                "description": "Incident state",
+                "enum": [
+                  "unknown",
+                  "investigating",
+                  "identified",
+                  "monitoring",
+                  "resolved"
+                ],
+                "type": "string"
+              },
+              "status": {
+                "description": "Incident status",
+                "enum": [
+                  "ongoing",
+                  "recovering",
+                  "recovered"
+                ],
+                "type": "string"
+              },
+              "title": {
+                "description": "Incident title",
+                "examples": [
+                  "Service is not working as expected"
+                ],
+                "type": "string"
+              }
+            },
+            "title": "Incident",
+            "type": "object"
+          }
+        ]
+      },
+      "type": "array"
+    },
+    "availability": {
+      "description": "Average availability of all associated monitors over the status page timeframe (30, 60 or 90 days), in percents",
+      "examples": [
+        99.9999
+      ],
+      "format": "float",
+      "type": "number"
+    },
+    "components": {
+      "description": "Components of the status page and their current status",
+      "items": {
+        "anyOf": [
+          {
+            "properties": {
+              "availability": {
+                "description": "Availability over the status page timeframe, in percents",
+                "examples": [
+                  99.9999
+                ],
+                "format": "float",
+                "type": "number"
+              },
+              "component_id": {
+                "examples": [
+                  1
+                ],
+                "type": "integer"
+              },
+              "component_type": {
+                "enum": [
+                  "uptime/monitor"
+                ],
+                "type": "string"
+              },
+              "current_incident_impact": {
+                "description": "Highest impact of the active incidents linked to the monitor, `maintenance` if there is no active incident and the monitor is in an in-progress maintenance window",
+                "enum": [
+                  "unknown",
+                  "operational",
+                  "maintenance",
+                  "degraded_performance",
+                  "partial_outage",
+                  "major_outage"
+                ],
+                "type": "string"
+              },
+              "name": {
+                "description": "Monitor display name, or its name when none is set",
+                "examples": [
+                  "Website"
+                ],
+                "type": "string"
+              },
+              "response_time": {
+                "description": "75th percentile (P75) response time of successful checks over the last 7 days, in milliseconds. Null if unavailable or if response times are hidden on the status page",
+                "examples": [
+                  123
+                ],
+                "type": [
+                  "integer",
+                  "null"
+                ]
+              }
+            },
+            "title": "Monitor component",
+            "type": "object"
+          },
+          {
+            "properties": {
+              "availability": {
+                "description": "Average availability of the group components over the status page timeframe, in percents",
+                "examples": [
+                  99.9999
+                ],
+                "format": "float",
+                "type": "number"
+              },
+              "component_type": {
+                "enum": [
+                  "uptime/group"
+                ],
+                "type": "string"
+              },
+              "components": {
+                "description": "Components of the group",
+                "items": {
+                  "properties": {
+                    "availability": {
+                      "description": "Availability over the status page timeframe, in percents",
+                      "examples": [
+                        99.9999
+                      ],
+                      "format": "float",
+                      "type": "number"
+                    },
+                    "component_id": {
+                      "examples": [
+                        1
+                      ],
+                      "type": "integer"
+                    },
+                    "component_type": {
+                      "enum": [
+                        "uptime/monitor"
+                      ],
+                      "type": "string"
+                    },
+                    "current_incident_impact": {
+                      "description": "Highest impact of the active incidents linked to the monitor, `maintenance` if there is no active incident and the monitor is in an in-progress maintenance window",
+                      "enum": [
+                        "unknown",
+                        "operational",
+                        "maintenance",
+                        "degraded_performance",
+                        "partial_outage",
+                        "major_outage"
+                      ],
+                      "type": "string"
+                    },
+                    "name": {
+                      "description": "Monitor display name, or its name when none is set",
+                      "examples": [
+                        "Website"
+                      ],
+                      "type": "string"
+                    },
+                    "response_time": {
+                      "description": "75th percentile (P75) response time of successful checks over the last 7 days, in milliseconds. Null if unavailable or if response times are hidden on the status page",
+                      "examples": [
+                        123
+                      ],
+                      "type": [
+                        "integer",
+                        "null"
+                      ]
+                    }
+                  },
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              "current_incident_impact": {
+                "description": "Highest current incident impact of the group components",
+                "enum": [
+                  "unknown",
+                  "operational",
+                  "maintenance",
+                  "degraded_performance",
+                  "partial_outage",
+                  "major_outage"
+                ],
+                "type": "string"
+              },
+              "name": {
+                "description": "Group name",
+                "examples": [
+                  "Websites"
+                ],
+                "type": "string"
+              },
+              "response_time": {
+                "description": "Average response time of the group components, in milliseconds",
+                "examples": [
+                  123
+                ],
+                "type": [
+                  "integer",
+                  "null"
+                ]
+              }
+            },
+            "title": "Group component",
+            "type": "object"
+          }
+        ]
+      },
+      "type": "array"
+    },
+    "current_incident_impact": {
+      "description": "Highest impact of all the active incidents linked to the status page, `maintenance` if there is no active incident and a maintenance window linked to the status page is in progress",
+      "enum": [
+        "unknown",
+        "operational",
+        "maintenance",
+        "degraded_performance",
+        "partial_outage",
+        "major_outage"
+      ],
+      "type": "string"
+    },
+    "updated_at": {
+      "description": "Date of the data calculation",
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds some value by clarifying that this is a derived, point-in-time snapshot aggregating incidents, maintenance, availability and component states, but says nothing about permissions needed or how the timeframe is determined.

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?

One sentence, front-loaded with the core action and then a compact enumeration of returned facets. Every clause conveys distinct information about what the agent will receive; there is no filler.

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 only two required, fully documented parameters, rich read-only annotations and an output schema that defines the return shape, the definition needs only to explain the nature of the data. It does that well; the main omission is the relationship to the similarly named get_status_page sibling.

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% and both parameters are documented in the input schema (project_id with a pointer to whoami, status_page_id). The description adds no additional meaning about these parameters, so the 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?

A specific verb+resource ('Get what a status page shows right now') followed by an enumeration of exactly what the response contains: active incident/maintenance impact, availability over the timeframe, per-component status, and published incidents. That is clear and informative, but it never differentiates itself from the sibling get_status_page, whose name is close enough that an agent could pick either.

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

Usage Guidelines2/5

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

The phrase 'right now' implies a live/computed view rather than stored configuration, but there is no explicit when-to-use guidance, no exclusion of get_status_page or list_incidents, and no stated prerequisites (e.g. whether the page must be published). The agent must infer that this is the read-live-state tool.

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

All Phare toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources