Skip to main content
Glama
AWS Health MCP Server

AWS Health MCP Server

Official
by aws-samples

get_service_health

Read-onlyIdempotent

Retrieves active and upcoming AWS service health events with descriptions and timelines, optionally filtered by region, to help identify service disruptions.

Instructions

Get current AWS service health events.

Returns active and upcoming AWS health events with descriptions and timelines. Consider summarize_health_events first: this returns full descriptions and can be very large on a busy account.

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

Example prompts:

  • "Show me all current AWS service health issues"

  • "What's broken in us-west-2?"

  • "Are there any active AWS service disruptions?"

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

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

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely non-structured context: results include active and upcoming events with descriptions and timelines, and the payload can be very large on a busy account. It stops short of describing pagination, limits, or whether org-wide data is excluded, which is a modest remaining gap.

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?

Core guidance is front-loaded in the first two sentences, with the size warning and alternative before the args block. The three example prompts are largely redundant with one another and add length without new information, which keeps it below top marks.

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 a single optional parameter, full annotation coverage, and an output schema that carries the return shape, the description supplies everything an agent needs: purpose, scope, the preferred alternative for large payloads, and parameter semantics. The one unstated nuance is account-level versus org-level scope, but the sibling naming convention plus the summarize_health_events hint makes the boundary discoverable.

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 schema only shows a nullable array of strings named "regions". The description compensates by stating that regions is optional, that it restricts results to AWS regions, and by giving a concrete example value ['us-west-2']. That is a meaningful supplement, though it does not explain case/format expectations or behavior when a region has no events.

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 opens with a specific verb and resource ("Get current AWS service health events") and clarifies the scope as "active and upcoming" events, which separates it from get_completed_events and get_scheduled_changes. It also names the sibling it is not (summarize_health_events), so an agent can route correctly without opening a schema.

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

Usage Guidelines5/5

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

It gives an explicit alternative and the condition that selects it: "Consider summarize_health_events first: this returns full descriptions and can be very large on a busy account." The example prompts reinforce the intended scenarios (account-wide issues, region-specific outages). Nothing about when to prefer the other tool is left to inference.

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