OpenUptime

list_maintenance

Read-onlyIdempotent

Retrieve authenticated maintenance windows for a project, with schedules and monitor associations, to plan downtime and check affected monitors.

Instructions

Read maintenance windows in the selected project, including schedule and monitor associations. Use this authenticated list for planning; list_public_status_page_maintenance only shows windows for a published page slug. This tool does not schedule downtime; use the app or REST API to create or remove windows.

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_maintenance"
  }
}

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, and the description adds context beyond them: the call is authenticated, its scope is the selected project, and it returns schedule plus monitor associations. It does not mention pagination or result limits, so not a full 5, but it meaningfully extends the annotation profile.

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 sentences, each with a distinct job: what it returns, which sibling to prefer, and what it cannot do. The scope and content 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?

No output schema exists, and the description compensates by naming what is returned (windows with schedule and monitor associations). With both params fully documented in the schema and auth/scope covered, only result-shape details like pagination or empty-result behavior are 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% — both project and workspace are described in the schema, including the defaulting behavior and provenance (from list_workspaces). The description only restates the project scoping implicitly ('in the selected project') and adds no format or precedence details, 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 ('Read maintenance windows') plus scope ('in the selected project') and content ('schedule and monitor associations'). It explicitly contrasts with the sibling list_public_status_page_maintenance, so an agent can pick between them 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?

Gives an explicit when-to-use ('this authenticated list for planning') and names the alternative with its distinguishing condition (list_public_status_page_maintenance only covers a published page slug). It also states out-of-scope operations and routes them elsewhere: 'does not schedule downtime; use the app or REST API to create or remove windows.'

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