Skip to main content
Glama
AWS Health MCP Server

AWS Health MCP Server

Official
by aws-samples

get_org_affected_entities

Read-onlyIdempotent

Retrieve affected AWS resources and entities for organization-wide health events, filtered by account ID or event ARN to identify what current AWS issues impact.

Instructions

Get affected entities for AWS health events across your organization.

Args: account_id: Optional. The AWS account ID to filter events for. event_arn: Optional. The ARN of a specific event to get details for.

Example prompts:

  • "What resources are affected by current AWS issues across my organization?"

  • "Show me impacted entities in account 123456789012"

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

Input Schema

NameRequiredDescriptionDefault
event_arnNo
account_idNo

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 covered by structured data. The description adds that results span the whole organization, which hints at elevated org-level access needs, but it never states permission requirements, whether unfiltered calls return results across all accounts, or the result volume implications of 'across your organization'.

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 sentence is front-loaded and the Args block plus two examples are compact and relevant. The docstring-style formatting is slightly mechanical for a tool description but wastes no words.

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 values need not be described, and annotations cover side-effect behavior; the remaining need is filter semantics. The description covers each parameter's intent and gives usage examples, leaving only the all-optional default case unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 supply one-line meanings for both parameters (account_id as an event filter, event_arn as a specific-event selector). It does not explain the combination semantics — notably what happens when both are omitted, which matters because both are optional with null defaults — so compensation is only partial.

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 names a specific verb and resource ('Get affected entities') and scopes it with 'for AWS health events across your organization', which distinguishes it from the single-account sibling get_affected_entities. It stops short of naming that sibling explicitly, so the differentiation relies on the reader inferring the org-wide scoping.

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 context is only implied: the two example prompts show typical calls (org-wide and per-account), but there is no statement of when to prefer this over get_affected_entities, get_event_details, or count_affected_entities. An agent can pattern-match the examples but gets no explicit routing rules or exclusions.

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