Skip to main content
Glama

Delete a maintenance window

delete_maintenance_window
DestructiveIdempotent

Deletes a maintenance window, every occurrence of a repeating one included. Subscribers told about an occurrence that has not started hear it is cancelled. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "window_id": "<window_id>"
    },
    "name": "delete_maintenance_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
window_idYesMaintenance window ID from list_maintenance_windows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description earns credit for disclosing that subscribers to a not-yet-started occurrence are notified of cancellation and that repeated occurrences are all removed, but it says nothing about authorization requirements, whether the deletion is recoverable, or what happens to in-progress occurrences.

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?

Two short sentences are front-loaded with the deletion scope, followed by the subscriber notification effect. The trailing 'Free.' is a single word of cost information that is useful but cryptic in isolation, costing it a point versus a fully polished phrasing.

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 one-parameter destructive delete with no output schema and full annotation coverage, the definition supplies the key operational facts: the repeating-occurrence blast radius and the cancellation notices sent to subscribers. Permission requirements and post-deletion state are the only meaningful omissions.

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?

With a single parameter at 100% schema description coverage, the schema already explains that window_id comes from list_maintenance_windows. The description adds no format, sourcing, or validation detail beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Deletes a maintenance window') and adds a precise scope: every occurrence of a repeating window is removed. This implicitly distinguishes it from occurrence-level operations, but it never names a sibling tool, so the differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this versus update_maintenance_window or change_maintenance_occurrence, and no stated prerequisites or confirmation requirements. The only usable signal is the scope note about repeating windows, which an agent must interpret as a reason to prefer this tool over single-occurrence changes.

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