Skip to main content
Glama
AWS Health MCP Server

AWS Health MCP Server

Official
by aws-samples

get_scheduled_changes

Read-onlyIdempotent

Retrieve upcoming AWS maintenance windows, planned service updates, and infrastructure changes by region to plan around potential service disruptions.

Instructions

Get all scheduled changes/maintenance events across AWS services.

Returns upcoming maintenance windows, planned updates, and infrastructure improvements.

Args: regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2'].

Example prompts:

  • "What maintenance is planned for AWS services?"

  • "Any upcoming maintenance in eu-west-1?"

  • "When is the next AWS 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": "get_scheduled_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.1
    • addedInput schema / properties / regions
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Regions"
      +}
  2. First observedv2.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds useful content-level context in saying the results are upcoming maintenance windows and planned improvements, but says nothing about pagination, time horizons, or what happens when regions is omitted (implicitly all regions).

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 core purpose and return contents are front-loaded in the first two lines, and the Args block is compact. The three example prompts add intent-matching value, though they repeat the same idea three times and slightly dilute the signal-to-noise ratio.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one optional parameter, full annotation coverage, and an output schema that documents the return shape, the description covers everything the agent needs in order to call it correctly. The only residual gap — org-level versus account-level scoping — is a sibling-differentiation issue rather than a completeness issue.

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 description coverage is 0%, so the description must compensate — and it does, marking regions as optional, defining its meaning (restrict to these AWS regions), and giving a concrete format example ['us-west-2']. It stops short of stating the default and whether the strings must match exact region codes.

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: retrieving scheduled changes/maintenance events across AWS services, with a follow-up sentence enumerating what is returned (maintenance windows, planned updates, infrastructure improvements). It does not, however, distinguish itself from the similarly named sibling get_org_scheduled_changes or from get_service_events, so the agent must infer the boundary.

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 example prompts ("What maintenance is planned for AWS services?", "Any upcoming maintenance in eu-west-1?") implicitly signal the intended use cases and intents well. There is no explicit when-not guidance and no named alternative such as get_org_scheduled_changes for organization-level scope, leaving the routing decision to inference.

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