Skip to main content
Glama

List incidents and maintenance

list_incidents
Read-only

Use this when the user asks what went down, whether anything is down now, what happened last night or this month, or what maintenance is planned. Returns incidents (open or resolved, with how each was confirmed) or maintenance windows, for one site, a group or the account, newest first. Not for one incident's full evidence: use get_incident.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_incidents"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoInstead of range: where the window ends, a date (the whole day is included) or RFC 3339.
fromNoInstead of range: where the window starts, a date such as 2026-07-01 (in your time zone) or RFC 3339. Goes with to. A window is at most 90 days, within the history your plan keeps.
kindNoIncidents or maintenance windows (default incident).
siteNoOnly this site: its id, name or part of its URL.
groupNoOnly sites in this group (exact name).
limitNoMost items to return (default 25).
rangeNoHow far back (default 30d). Clamped to the history your plan keeps.
statusNoOpen, resolved or both (default all).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond that: results are newest-first and resolved incidents include how each was confirmed, plus the fact that kind selects incident vs maintenance windows. It does not mention result truncation or that the effective history window is the plan's limit, which keeps it off a 5.

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?

Three short sentences with the usage trigger front-loaded, the return shape in the middle, and the sibling exclusion last. No restatement of the tool name or wasted clauses; every sentence carries information.

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?

There is no output schema, and the description compensates by describing what comes back: incidents (open or resolved, with confirmation method) or maintenance windows, ordered newest first, scoped to a site/group/account. Combined with 100% parameter documentation and read-only annotations, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents every parameter, its enums and defaults — the baseline is 3. The description adds a small but genuine semantic layer by framing site/group/account as the three scoping modes the filters implement, which helps an agent understand how site and group relate rather than treating them as independent filters.

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 (lists incidents and maintenance windows), names the returned scope (one site, a group, or the account), and explicitly distinguishes itself from the sibling get_incident. An agent can route between the two without opening either 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?

Opens with concrete user-intent triggers ("what went down", "anything down now", "what happened last night", "what maintenance is planned") and ends with an explicit exclusion plus the alternative to use instead (get_incident for one incident's evidence). Both when-to-use and when-not-to-use are covered.

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.

Resources