Skip to main content
Glama
AWS Health MCP Server

AWS Health MCP Server

Official
by aws-samples

get_service_events

Read-onlyIdempotent

Retrieve AWS Health events for a specific service and optional regions to check current issues and operational problems affecting that service.

Instructions

Get health events for a specific AWS service.

Args: service: The AWS service name (e.g., 'EC2', 'RDS', 'LAMBDA'). Case insensitive. Use list_event_types to discover the codes AWS Health uses. regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2'].

Example prompts:

  • "What's happening with EC2 right now?"

  • "Any RDS issues in eu-west-1?"

  • "Are there any problems with S3?"

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "service": "<service>"
    },
    "name": "get_service_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionsNo
serviceYes

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

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile needs no restating. The description adds the useful traits of case-insensitive service matching and optional region narrowing, but says nothing about result scope (open vs. resolved events, default time window) or pagination limits that would matter for a potentially large health feed.

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 opening sentence front-loads the purpose, followed by a compact Args block and three short mappable example prompts; nothing is padded. The misplaced list_event_types sentence is the only line that does not clearly earn its place where it sits.

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?

Both parameters are documented, an output schema exists so return values need no explanation, and the example prompts cover the common query shapes. Completeness would be higher if it clarified the event window/filter defaults or whether results include resolved events, since there is no time-range parameter to fall back on.

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?

With 0% schema description coverage, the description carries the full burden and largely meets it: it gives sample service values ('EC2', 'RDS', 'LAMBDA'), states case insensitivity, and gives an example region list format for the optional regions array. The one blemish is the note to "use list_event_types to discover the codes AWS Health uses" attached to `service`, which takes service names rather than event-type codes and is therefore mildly confusing.

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 health events for a specific AWS service" names a concrete verb (get) and a concrete resource (health events) scoped to a service, which is clearly distinguishable from get_event_details or summarize_health_events. It stops short of explicitly contrasting itself with the closest sibling, get_service_health, so an agent must infer the events-vs-aggregate-health 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's happening with EC2 right now?", "Any RDS issues in eu-west-1?") implicitly show when to reach for this tool, which is real guidance. However, there is no explicit when-not-to-use or pointer to the competing siblings (get_service_health, get_org_service_events, get_scheduled_changes), so the routing decision is left inferred.

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