Skip to main content
Glama

Maintenance windows

list_maintenance_windows
Read-only

Maintenance windows, latest first: times when failures open no incidents and send no alerts, for one monitor or all. A repeating window has its recurrence in words (repeats), its next occurrences and the ones skipped or moved. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: result ordering ('latest first'), the shape of repeating windows (recurrence in words, next occurrences, skipped or moved ones), and the terse 'Free' note implying no quota cost. The one-word 'Free' is ambiguous and could mislead an agent about rate limits.

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?

Front-loaded with resource and ordering, then the definition, then the return shape for repeating windows. It is dense but each clause carries information; only 'Free' is an unexplained fragment that costs clarity.

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?

With no parameters and no output schema, the description carries the burden of explaining what comes back, and it does so for both simple and repeating windows. Minor gaps remain around pagination and the meaning of 'Free', but an agent can call this correctly as written.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. The phrase 'for one monitor or all' actually helps by signaling that scope is not an input choice but a property of the returned data.

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 identifies the resource (maintenance windows) and the ordering ('latest first'), plus defines what a window means operationally ('times when failures open no incidents and send no alerts'). It is clear this is the listing counterpart to create/update/delete_maintenance_window, though it never uses an explicit verb like 'list' and leans on the name for that.

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

Usage Guidelines3/5

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

'for one monitor or all' implies the returned scope, and the sibling set makes the read-vs-mutate split fairly obvious. However, there is no explicit when-to-use statement, no mention of pagination or filtering limits, and no pointer to change_maintenance_occurrence for the skipped/moved occurrences it advertises.

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