Skip to main content
Glama

mcp-uptimerobot__list-maintenance-windows

Read-onlyIdempotent

List maintenance windows for the authenticated user. Requires a plan with the maintenance-window feature. Pass the returned cursor to fetch the next page. Through Royally: its server marks it read-only, so it runs straight away.

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": "mcp-uptimerobot__list-maintenance-windows"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor (maintenance window ID) for the next page
site_idNoSite to run this tool on: 0b6d9b21-ca64-4476-bc68-d1cd935ca7cb (https://mcp.uptimerobot.com/mcp)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so the safety profile is free. The description does add genuine context beyond them: the plan/feature gating that can cause failure, and the fact that the gateway executes it without a confirmation step. It says nothing about page size limits or what a failure looks like when the plan lacks the feature.

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 purpose and prerequisite are front-loaded and each sentence is short. The closing 'Through Royally' sentence is somewhat chatty gateway narration that largely re-states the readOnly annotation, but it is brief and does convey the no-approval execution path.

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 two-parameter read-only list tool with no output schema, the description covers purpose, access prerequisite, and pagination mechanics. What is missing is minor: nothing about page size or the fields a maintenance window entry carries, though the reference to a 'returned cursor' at least implies the response shape.

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%, so the schema already explains both cursor and site_id. The description only reinforces cursor usage ('Pass the returned cursor to fetch the next page') without adding format or bounds information beyond the schema's 'maintenance window ID' note. Baseline 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 first sentence states a specific verb and resource ('List maintenance windows') with the scope qualifier 'for the authenticated user,' which cleanly separates it from the singular get-maintenance-window sibling. It stops short of an explicit contrast with that sibling, so 4 rather than 5.

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?

It gives a real prerequisite ('Requires a plan with the maintenance-window feature') and tells the agent how to continue paginating. It never states when to choose this over get-maintenance-window or the other list tools, so usage is implied rather than routed.

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