Skip to main content
Glama
AWS Health MCP Server

AWS Health MCP Server

Official
by aws-samples

get_org_service_health

Read-onlyIdempotent

Get current AWS service health events across your organization.

Instructions

Get current AWS service health events across your organization.

Provides a comprehensive overview of active health events across all accounts in your AWS Organization.

Example prompts:

  • "Show me all current AWS service health issues across my organization"

  • "Are there any active AWS service disruptions affecting multiple accounts?"

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds only the scope detail that results span all accounts in the organization and cover 'active'/'current' events, with nothing on pagination, volume, or how results are aggregated across accounts.

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

Conciseness3/5

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

The core scope statement is front-loaded, which is good, but the second sentence ('comprehensive overview of active health events across all accounts in your AWS Organization') largely restates the first line and does not earn its space. The example prompts are short and mildly useful but repeat the same idea a third time.

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 zero parameters and an output schema present, the description need not explain return values, and it adequately conveys scope and currency of the data. The remaining gap is sibling differentiation among the many org-scoped tools, which the description never addresses.

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?

The tool takes zero parameters, so there is no parameter meaning to convey; baseline 4 applies. The description correctly implies the call is unfiltered and org-wide, which is consistent with an empty argument object.

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?

States a specific verb and resource ('Get current AWS service health events') plus a clear scope ('across your organization', 'all accounts in your AWS Organization'), which separates it from the account-level get_service_health. However, it gives no signal for distinguishing it from near-identical org-scoped siblings such as get_org_health_events, get_org_service_events, and get_org_account_events, leaving real ambiguity.

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 two example prompts imply the usage context (org-wide, multi-account disruption checks), which is helpful but indirect. There is no explicit when-to-use vs. when-not guidance and no named alternative among the 17 siblings, so an agent must infer routing from the tool name alone.

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