Skip to main content
Glama
AWS Health MCP Server

AWS Health MCP Server

Official
by aws-samples

get_completed_events

Read-onlyIdempotent

Retrieve completed or closed AWS Health events and filter them by service or region to review resolved incidents and past service issues.

Instructions

Get completed/closed health events.

Args: service: Optional. The AWS service name to filter by. Case insensitive. regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2'].

Example prompts:

  • "Show me recently resolved AWS issues"

  • "What EC2 problems were fixed in us-east-1?"

  • "Get history of resolved incidents"

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

Input Schema

NameRequiredDescriptionDefault
regionsNo
serviceNo

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.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 covered. The description adds that filtering is case insensitive and shows region-list syntax, but says nothing about result ordering, pagination/limits, or retention window for 'completed' events — meaningful gaps even with annotations present.

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?

Front-loaded with a one-line purpose, then Args, then example prompts — easy to scan and nothing is wasted. The Args block repeats 'Optional' which the schema defaults already convey, a minor redundancy.

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

Completeness3/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 values need not be described, and the read-only annotations cover safety. Still missing for a history-retrieval tool: result ordering/recency, any cap on returned events, and what happens with no filters — an agent cannot predict the result shape or volume.

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 carries the full burden and largely delivers: it states both params are optional, that service is case insensitive, and gives a concrete region format (['us-west-2']), which prevents malformed calls. It does not state the default behavior when both are omitted (all services/regions?), which is the remaining gap.

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?

"Get completed/closed health events" gives a specific verb (get) and a resource narrowed by lifecycle state (completed/closed), which distinguishes it from the open-event siblings like get_service_events or get_org_service_events. It stops short of naming those siblings explicitly, so the distinction is inferred from the 'completed' qualifier rather than stated.

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 ('Show me recently resolved AWS issues', 'What EC2 problems were fixed in us-east-1?') implicitly show the when-to-use case and illustrate both filters in combination. However, there is no explicit when-not guidance, no mention of what to call for active/unresolved events, and no statement of prerequisites or account scope.

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