OpenUptime

list_incidents

Read-onlyIdempotent

Find open and manual incidents in a project, with open incidents first, and return summaries and UUIDs for investigation or follow-up.

Instructions

Find automatic and manually opened incidents visible in the selected project, with open incidents first. Returns incident summaries and UUIDs; use get_incident for the timeline, failed checks and investigation details. To change status or resolve an incident, use post_incident_update rather than update_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

Name	Required	Description	Default
`project`	No	Project id (from list_workspaces). Omit to use the default project of the workspace.
`workspace`	No	Workspace id (from list_workspaces). Omit to use the default one.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds value beyond that by disclosing the return shape (incident summaries and UUIDs) and the open-first ordering, which annotations cannot express. It stops short of noting result limits or pagination.

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, each doing distinct work: what it lists, what it returns, and where to go instead. Scoping and ordering are front-loaded with 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?

For a two-optional-parameter read tool with no output schema, the description covers purpose, return contents, and sibling routing adequately. Minor gap: no mention of pagination, result caps, or whether closed/resolved incidents are included.

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%; both project and workspace carry their own descriptions including the omit-to-use-default behavior. The description only vaguely refers to 'the selected project' and adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 plus scope: incidents (automatic and manually opened) visible in the selected project. It also specifies result ordering (open incidents first), so an agent knows exactly what this returns relative to siblings like list_maintenance or get_incident.

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 routes the agent: use get_incident for timeline/failed checks/investigation details, and use post_incident_update (not update_incident) to change status or resolve. That is concrete when-to-use and when-not-to-use guidance naming three alternatives.

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