Skip to main content
Glama
Sign In

InfraNest

by io.infranest
OverviewDiscussionsAdmin

List maintenance windows

list_maintenance_windows
Read-onlyIdempotent

A paginated list of your maintenance windows with the monitors, servers and tags each window covers, whether each window is in effect and its current or next occurrence, plus counts in meta. Filter with search, tag and status (active, scheduled, recurring or completed), and sort with sort (schedule, name, monitors or status) and dir. active: running now, alerts silenced; scheduled: coming up. To open or end one use start_maintenance or end_maintenance.

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
tagNoOnly things with this tag id.
pageNoPage number, from 1.
searchNoMatches name or description.
statusNoactive: alerts are silenced right now.
per_pageNoRows per page, up to 200 (default 25).
organization_idNoThe organization to read. Leave it out when the token reaches only one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description's extra value is in disclosing the return shape and status semantics. It explains that results include covered monitors/servers/tags, active state, current/next occurrence, and meta counts, and it defines active and scheduled filters. It does not cover auth or rate-limit behavior, but the key operational traits are present.

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?

The description is front-loaded with the return shape and then covers filtering, sorting, and alternatives. It is dense but nearly every clause adds useful information; the first sentence is long and could be split for readability.

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 output schema, the description carries the burden of explaining the return shape, and it does so by naming covered entities, active state, occurrence data, and meta counts. It is largely complete for an agent to call the tool correctly, though the mismatch between the mentioned sort/dir parameters and the schema leaves a small completeness gap.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds useful semantics for filtering and sorting, including sort values and status meanings. It also mentions sort and dir even though those do not appear in the input schema, which is helpful but slightly inconsistent with the provided 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?

The description gives a specific verb and resource ('A paginated list of your maintenance windows') and immediately states what each result contains: monitors, servers, tags, active state, current/next occurrence, and meta counts. It is clearly distinguishable from mutation siblings and from generic list tools.

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

Usage Guidelines4/5

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

It explains how to filter and sort and explicitly routes mutation actions to start_maintenance or end_maintenance. It does not state when to prefer this tool over a broader sibling like search, but the usage context is clear enough to act on.

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

All InfraNest toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources