Skip to main content
Glama
AWS Health MCP Server

AWS Health MCP Server

Official
by aws-samples

get_org_account_events

Read-onlyIdempotent

Retrieve AWS Health events for a specific account in your organization, optionally filtered by AWS regions, to identify issues and scheduled maintenance affecting that account.

Instructions

Get health events for a specific AWS account in your organization.

Args: account_id: The 12-digit AWS account ID. regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2'].

Example prompts:

  • "What health events are affecting account 123456789012?"

  • "Show me all issues in my account"

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": {
      "account_id": "<account_id>"
    },
    "name": "get_org_account_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionsNo
account_idYes

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 readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds the 12-digit account ID format and the region-restriction behavior, which is real value, but says nothing about whether results are live or historical, or about volume, even though these are open-world health 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 core purpose is front-loaded in one sentence, followed by compact arg notes and illustrative prompts. The second prompt ('Show me all issues in my account') is slightly redundant with the first and adds little, but overall there is no significant padding.

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?

An output schema exists, so return-value explanation is not needed, and both parameters are documented in the description despite zero schema coverage. For a two-parameter read-only query tool this is close to sufficient; only the org-vs-global scoping boundary remains unstated.

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 burden and largely meets it: account_id is pinned to a 12-digit AWS account ID, and regions is marked optional with a concrete example list format. The null-default semantics of regions are not explained, but the essential calling contract is clear.

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') scoped to a single AWS account within an organization, which lets an agent separate it from the broader org-level sibling get_org_health_events. It stops short of naming that sibling or any other alternative, so the differentiation is implicit 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?

Usage is conveyed only through example prompts ('What health events are affecting account ...?'), which imply the single-account lookup scenario but never state when to prefer this over get_org_health_events, get_service_events, or get_event_details. No exclusions or prerequisites are given.

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