fettle-mcp

by fettlesh

Overview Schema Source Related Servers Discussions Admin

TypeScript

List maintenance windows

list_maintenance_windows

Read-onlyIdempotent

Find a maintenance window's ID by listing every organization window, enabled or not, in effect or not.

Instructions

List every maintenance window of the organization, enabled or not, in effect or not. Each has id, name, enabled, scope (ORG or MONITOR), dtstart, duration_minutes, rrule, timezone, monitor_ids and created_at. Use it to find a window's id. To learn whether alerts are silenced right now use list_active_maintenance; for a window's upcoming occurrences use get_maintenance_window. Returns a page: items plus total, page, size and pages.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Case-insensitive substring of the name, up to 255 characters.
`page`	No	Page number, 1 or more; default 1.
`size`	No	Rows per page, 1 to 100; default 25. Keep paging until you have seen total rows.
`sort`	No	created_at (the default, newest first) or name.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page`	Yes
`size`	Yes
`items`	Yes
`pages`	Yes
`total`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.6.1Oct 20, 2026

addedInput schema / properties / page / description

Added value: +"Page number, 1 or more; default 1."

addedInput schema / properties / q / description

Added value: +"Case-insensitive substring of the name, up to 255 characters."

addedInput schema / properties / size / description

Added value: +"Rows per page, 1 to 100; default 25. Keep paging until you have seen total rows."

addedInput schema / properties / sort / description

Added value: +"created_at (the default, newest first) or name."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "items": {
+        "properties": {
+          "created_at": {
+            "type": "string"
+          },
+          "dtstart": {
+            "type": "string"
+          },
+          "duration_minutes": {
+            "type": "integer"
+          },
+          "enabled": {
+            "type": "boolean"
+          },
+          "id": {
+            "format": "uuid",
+            "type": "string"
+          },
+          "monitor_ids": {
+            "items": {
+              "format": "uuid",
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "name": {
+            "type": "string"
+          },
+          "rrule": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "scope": {
+            "description": "Known values: MONITOR, ORG.",
+            "type": "string"
+          },
+          "timezone": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "enabled",
+          "scope",
+          "dtstart",
+          "duration_minutes",
+          "rrule",
+          "timezone",
+          "created_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "page": {
+      "type": "integer"
+    },
+    "pages": {
+      "type": "integer"
+    },
+    "size": {
+      "type": "integer"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "items",
+    "total",
+    "page",
+    "size",
+    "pages"
+  ],
+  "type": "object"
+}

First observedv0.5.4Oct 20, 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 the safety profile is covered. The description goes beyond that by disclosing that results include both enabled and disabled windows and both active and inactive ones, enumerating the returned fields, and describing the paginated envelope (items plus total, page, size, pages). It stops short of rate-limit or auth notes, so not 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with the purpose and scope front-loaded and the sibling routing immediately after. The field enumeration is somewhat redundant given an output schema exists, which keeps it from a 5, but nothing is padded.

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?

With annotations covering safety, a 100%-covered input schema, and an output schema present, the description need not restate return structure in detail yet still does enough to orient the agent. Everything needed to call it correctly — scope, use case, alternatives — is present.

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 each parameter (q, page, size, sort) is already documented in the schema, including defaults and paging advice. The description adds nothing about parameter semantics, so the baseline of 3 is appropriate.

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 (List) and resource (maintenance windows of the organization) with explicit scope: enabled or not, in effect or not. It further separates itself from siblings by naming list_active_maintenance and get_maintenance_window, so an agent can pick it without opening any 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 a concrete use case ('Use it to find a window's id') and explicitly routes to alternatives with conditions: list_active_maintenance for current silencing state, get_maintenance_window for upcoming occurrences. This is exactly the when-to-use/when-not guidance the dimension asks for.

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

Deploy Server