Skip to main content
Glama
AWS Health MCP Server

AWS Health MCP Server

Official
by aws-samples

get_affected_entities

Read-onlyIdempotent

Lists affected AWS entities for all open health events, grouped by event and status, to help identify resources experiencing active issues.

Instructions

Get affected entities for all open AWS health events.

Shows resources impacted by active health events, grouped by event and status.

Example prompts:

  • "What resources are affected by current AWS issues?"

  • "Show me all impacted AWS entities"

  • "Which AWS resources are experiencing problems?"

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

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, idempotentHint, openWorldHint, and destructiveHint=false, so safety and idempotency are covered by structured fields. The description adds genuine behavioral context by stating the result set is limited to open/active events and that output is grouped by event and status. It does not mention pagination, result-size limits, or any permission/API-access requirements, which matters for an openWorld tool.

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 scope statement is front-loaded in the first two sentences with zero filler. The three example prompts are compact but largely paraphrase one another ('affected', 'impacted', 'experiencing problems'), so the block adds phrasing variety for retrieval more than new information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 needn't be explained, and annotations cover the safety profile, making the description's coverage of scope and grouping reasonable. The remaining gap is sibling disambiguation: with get_org_affected_entities, count_affected_entities, and list_affected_accounts in the same family, an agent cannot confidently choose this tool from the description alone.

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 nothing for the description to disambiguate; the baseline for a parameterless schema is 4. The description correctly avoids inventing parameters and instead spends its words on scope.

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 first sentence names a specific verb ('get'), resource ('affected entities'), and scope ('all open AWS health events'), and the second clarifies that resources are grouped by event and status. That is far more than a restatement of the name. It stops short of 5 because it never distinguishes itself from near-identical siblings such as get_org_affected_entities or count_affected_entities.

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 implicitly define the usage context ('current AWS issues', 'experiencing problems'), which signals this is for live/open events rather than historical ones. However, there is no explicit when-not guidance and no routing statement separating it from get_org_affected_entities (org-wide) or count_affected_entities (counts only), which is the main ambiguity an agent would face with 17 siblings.

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