Skip to main content
Glama
AWS Health MCP Server

AWS Health MCP Server

Official
by aws-samples

get_org_health_events

Read-onlyIdempotent

Retrieve active or closed AWS Organization health events, filtered by service, account, status, or region, to identify issues affecting your accounts.

Instructions

Get health events across your AWS Organization.

If no arguments are provided, returns all active org health events.

Args: service: Optional. The AWS service name to filter by. Case insensitive. account_id: Optional. The AWS account ID to filter events for. status: Optional. 'active' (default) or 'closed'. regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2'].

Example prompts:

  • "Show me org-wide AWS health events"

  • "What issues affect account 123456789012?"

  • "Any org-wide events in ap-southeast-2?"

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

Input Schema

NameRequiredDescriptionDefault
statusNoactive
regionsNo
serviceNo
account_idNo

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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint. The description adds real value beyond that by disclosing the no-argument default behavior and the 'active' status default, but it says nothing about pagination, result limits, or the org-level permissions needed to read cross-account events.

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 behavior statement is front-loaded ahead of the parameter list, and each arg note is a single useful clause. The three example prompts are mildly redundant with the arg docs but still short and intent-mapping.

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?

With four optional parameters, no required inputs, and an output schema that covers return values, the description supplies enough to call the tool correctly. The remaining gap is operational detail such as pagination or result-set size, which an agent may need for large organizations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does: it names all four parameters, documents 'active'/'closed' for status (an enum the schema itself lacks), states service filtering is case insensitive, and gives a concrete regions list format example. This is meaning that is genuinely unavailable from 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 description states a specific verb and resource ("Get health events") with an explicit organizational scope ("across your AWS Organization"), which lets an agent separate it from the single-account siblings like get_service_health and get_service_events. It does not name any sibling explicitly, so it stops short of a 5.

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

Usage Guidelines4/5

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

It clearly establishes the org-wide context, states the zero-argument default ("returns all active org health events"), and the example prompts map realistic intents onto calls. There is no explicit exclusion telling the agent when to prefer get_org_service_events or get_org_account_events instead.

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