Skip to main content
Glama

mcp-uptimerobot__get-maintenance-window

Read-onlyIdempotent

Get a single maintenance window by ID. Requires a plan with the maintenance-window feature. Through Royally: its server marks it read-only, so it runs straight away.

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": {
      "maintenanceWindowId": "<maintenanceWindowId>"
    },
    "name": "mcp-uptimerobot__get-maintenance-window"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idNoSite to run this tool on: 0b6d9b21-ca64-4476-bc68-d1cd935ca7cb (https://mcp.uptimerobot.com/mcp)
maintenanceWindowIdYesID of the maintenance window to retrieve

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, idempotentHint=true, and destructiveHint=false, so the safety profile is structured data. The description's genuinely additive element is the feature-gating requirement, which tells the agent the call may fail for entitlement reasons; the remainder ("its server marks it read-only, so it runs straight away") largely restates the read-only annotation.

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, front-loaded with the action and resource, with no filler. The trailing clause about the Royally server being read-only is somewhat redundant against the annotations and could be dropped.

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 simple single-record read with a fully described two-parameter schema, complete annotations, and no output schema, the description covers the essentials: what it returns (one window), the required ID, and the plan prerequisite. It is only missing a pointer to the list alternative for discovery use cases.

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 coverage is 100%, so the maintenanceWindowId and site_id parameters are already documented, including the positive-integer constraint and the site enum. The description only restates that the lookup is by ID and adds no format, range, or site-selection guidance beyond the schema.

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 gives a specific verb and resource ("Get a single maintenance window by ID"), and the word "single" implicitly contrasts with the list-maintenance-windows sibling. It stops short of naming that sibling explicitly, so it is clear but not fully differentiated.

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?

The description names a prerequisite (a plan that includes the maintenance-window feature), which implies when the call will work, but it never states when to fetch a single window versus listing all windows. Usage must be inferred from the tool name and the presence of an ID parameter.

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