Skip to main content
Glama
AWS Health MCP Server

AWS Health MCP Server

Official
by aws-samples

get_org_service_events

Read-onlyIdempotent

Retrieve AWS Health events for a specific service across your organization, optionally filtered by region, to identify account-wide issues and scheduled maintenance.

Instructions

Get health events for a specific AWS service across your organization.

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

Example prompts:

  • "What's happening with EC2 across my organization?"

  • "Show me all RDS issues affecting my AWS accounts"

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_org_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.7/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 openWorldHint=true, so the safety profile is covered. The description adds that service names are case insensitive and that the region filter is optional, but says nothing about result limits, pagination, or whether the event set includes resolved/past events — meaningful gaps for an organizational health query.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is stated in the first sentence, parameter notes follow in a compact Args block, and two short example prompts close it out. No sentence is redundant with another, and the critical scope constraint is front-loaded.

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 an output schema present, return values need not be explained, and the read-only annotations remove the need for mutation caveats. What remains missing is query-shaping behavior such as time-window defaults or result caps, which matters for an open-world organizational query.

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 it does: 'service' is explained as an AWS service name with concrete examples ('EC2', 'RDS', 'LAMBDA') and case-insensitivity noted, while 'regions' is described as an optional list of AWS regions with an example value. That is a solid compensation for the undocumented 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 opens with a specific verb and resource ('Get health events for a specific AWS service') plus a clear scope ('across your organization'), which separates it from the account-scoped get_service_events and the all-service get_org_health_events. It stops short of naming those siblings explicitly, so the distinction relies on the reader inferring from scope wording.

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 hint at when the tool applies ('What's happening with EC2 across my organization?'), giving implied usage context. However, there is no explicit when-not-to-use guidance or pointer to the alternative tools (get_org_health_events, get_org_service_health, get_service_events) that an agent would need to pick correctly among 17 siblings.

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