Skip to main content
Glama

Statuspage Incidents

statuspage_incidents
Read-onlyIdempotent

Incident and outage history for a vendor's status page, what broke, when, and whether it is fixed. Covers 190 verified Atlassian Statuspage vendors across AI providers, clouds, developer platforms, payments and communications. Each incident returns its title, lifecycle status (investigating / identified / monitoring / resolved), impact level (none / minor / major / critical), the time it started, the time it resolved, how long it lasted, the affected components, and the text of the latest update the vendor posted. Set unresolved_only to see only incidents that are still open. Use for outage history, past downtime, current incidents and postmortem timelines. Pass status_host for vendors outside the curated map.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vendor": "cloudflare",
      "unresolved_only": true
    },
    "name": "statuspage_incidents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum incidents to return, 1-50 (default 10).
vendorNoVendor name or key, e.g. "cloudflare", "github", "anthropic".
status_hostNoStatuspage hostname to query directly, e.g. "status.somevendor.com". Overrides vendor when both are given.
unresolved_onlyNoReturn only incidents that are still open (default false).
include_all_updatesNoInclude the full update timeline for each incident rather than only the latest update (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds real value beyond that — the 190-vendor curated scope, the exact per-incident payload, and the status_host override — but says nothing about failure behavior (unknown vendor, unreachable host) or rate limits, so it adds context without full behavioral coverage.

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?

Purpose is front-loaded in the first sentence, followed by scope, return shape, and parameter hints in a logical order with no filler sentences. The vendor-category enumeration ('AI providers, clouds, developer platforms, payments and communications') is the one expendable clause, keeping it just short of a 5.

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 no output schema, the description correctly carries the return-value burden and enumerates title, status, impact, timestamps, duration, components, and latest update. Combined with the zero-required-parameter schema and annotations, an agent has nearly everything needed; only error/edge-case behavior for unknown vendors 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 description coverage is 100%, so all five parameters are already documented, and the description largely restates them (unresolved_only, status_host override, latest-update default). The only added meaning is the rationale that status_host is for 'vendors outside the curated map' and that each incident carries the latest vendor update by default; that is a modest increment over the schema, so 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 opening clause names a specific resource and scope: 'Incident and outage history for a vendor's status page, what broke, when, and whether it is fixed,' and the return-field list makes the operation unambiguous. It stops short of naming a sibling (e.g. statuspage_check) as the contrasting alternative, so differentiation is implied through the 'use for' sentence rather than stated.

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?

Provides clear usage context: 'Use for outage history, past downtime, current incidents and postmortem timelines,' plus guidance to set unresolved_only for open incidents and to pass status_host for vendors outside the curated map. It gives good positive triggers but no explicit when-not-to-use or named alternative tool, so it falls 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.