Skip to main content
Glama
fettlesh

fettle-mcp

by fettlesh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Delete a maintenance window

delete_maintenance_window
DestructiveIdempotent

Delete a maintenance window to immediately resume alerts for its monitors. Use update_maintenance_window with enabled false instead to suspend it without deleting.

Instructions

Delete one maintenance window; alerts for its monitors resume at once and no tool restores it. To suspend a window but keep it, use update_maintenance_window with enabled false. Requires a key with the write scope. Returns {"success": true}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
window_idYesThe window's uuid from list_maintenance_windows. An id that is not a window of this organization is a 404.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.1
    • addedInput schema / properties / window_id / description
      Added value: +"The window's uuid from list_maintenance_windows. An id that is not a window of this organization is a 404."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}
  2. First observedv0.5.4

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the effect is immediate ('alerts for its monitors resume at once'), it is unrecoverable ('no tool restores it'), and it requires a key with the write scope. The annotations declare destructiveHint=true, but the description tells the agent what is actually destroyed and that recovery is impossible.

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 tight clauses covering effect, alternative, and prerequisites, with the destructive consequence front-loaded. No filler sentences.

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?

For a destructive single-parameter tool, everything needed is present: irreversibility, side effect on monitors, the safer alternative, auth scope, and return shape. The output schema exists, so restating the return value is a minor redundancy rather than a gap.

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?

Only one parameter with 100% schema description coverage, so the schema already carries the semantics including the uuid format and the 404 condition. The description adds no additional parameter-level detail, which is the baseline 3 for a fully documented schema.

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 ('Delete one maintenance window') and immediately distinguishes it from the sibling update_maintenance_window by contrasting deletion with suspension. An agent can route correctly 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?

Explicitly names the alternative and the exact condition that selects it: 'To suspend a window but keep it, use update_maintenance_window with enabled false.' This is genuine when-to-use/when-not guidance rather than implied usage.

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

Deploy Server

Other Tools