Skip to main content
Glama
AWS Health MCP Server

AWS Health MCP Server

Official
by aws-samples

get_org_scheduled_changes

Read-onlyIdempotent

Retrieve upcoming scheduled maintenance and changes affecting accounts across your AWS Organization to plan for disruptions.

Instructions

Get scheduled changes/maintenance events across your AWS Organization.

Returns upcoming maintenance affecting accounts in your organization.

Example prompts:

  • "What maintenance is planned across my organization?"

  • "Show me upcoming AWS changes affecting my accounts"

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

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, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful behavior beyond that by scoping results to future/upcoming maintenance across org accounts, but it omits pagination, result volume, or how far ahead the window extends for an org-wide query.

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 definition is short and front-loaded: the core purpose appears in the first sentence, with the return content in the second. The example prompts add some length but serve as realistic invocation cues rather than filler.

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?

An output schema exists, so return-value detail is unnecessary, and with no parameters the description only needs to convey scope and timing. It does both, though it could note required org-level access or whether results aggregate across all accounts versus a subset of OUs.

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 there is no parameter semantics to explain and the baseline is 4. The description correctly implies the call is unfiltered and org-scoped, which is consistent with an empty argument object.

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 states a specific verb and resource ('Get scheduled changes/maintenance events') and pins the scope to 'across your AWS Organization' / 'affecting accounts in your organization'. This implicitly separates it from the account-scoped sibling get_scheduled_changes, but it never names that sibling or states the contrast explicitly, so an agent must infer the distinction from the 'org' prefix.

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?

Usage is conveyed only through two example prompts ('What maintenance is planned across my organization?'), which imply the org-wide, upcoming-maintenance scenario. There is no explicit when-not guidance, no mention of how this differs from get_scheduled_changes or get_org_health_events, and no stated prerequisites (e.g. org-level permissions).

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