Skip to main content
Glama

get_service_health

Monitor AWS service health by retrieving recent operational events from the AWS Health Dashboard to identify potential issues affecting your cloud infrastructure.

Instructions

Lists recent open events from AWS Health Dashboard.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that executes the tool logic: queries AWS Health API for open and upcoming events using DescribeEventsCommand and returns formatted JSON response.
    if (name === "get_service_health") {
        const command = new DescribeEventsCommand({
            filter: { eventStatusCodes: ["open", "upcoming"] }
        });
        const response = await healthClient.send(command);
    
        const events = response.events?.map(e => ({
            EventTypeCode: e.eventTypeCode,
            Service: e.service,
            Region: e.region,
            StartTime: e.startTime,
            Status: e.statusCode,
            Description: e.eventScopeCode
        })) || [];
    
        return {
            content: [{ type: "text", text: JSON.stringify(events, null, 2) }]
        };
    }
  • src/index.ts:550-556 (registration)
    Tool registration in the ListTools handler, defining name, description, and input schema (no parameters required).
        name: "get_service_health",
        description: "Lists recent open events from AWS Health Dashboard.",
        inputSchema: {
            type: "object",
            properties: {}
        }
    },
  • Initialization of the AWS HealthClient instance used exclusively by the get_service_health tool handler.
    const healthClient = new HealthClient({ region: "us-east-1" }); // AWS Health API is global (us-east-1)
  • Import of AWS SDK HealthClient and DescribeEventsCommand used in the tool implementation.
    import { HealthClient, DescribeEventsCommand } from "@aws-sdk/client-health";
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like whether results are paginated, time-bound, require specific permissions, or include rate limits. 'Lists recent open events' implies read-only and non-destructive, but lacks detail on what 'recent' means or output format.

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?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple tool with no parameters.

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?

For a zero-parameter tool with no annotations and no output schema, the description is minimally adequate. It states what the tool does but lacks context about output format, time ranges, or AWS account scope. Given the simplicity, it's complete enough to be functional but leaves gaps for effective agent use.

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 has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter semantics, but that's appropriate given the lack of parameters, warranting a baseline score above minimum.

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 clearly states the action ('Lists') and resource ('recent open events from AWS Health Dashboard'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'list_cloudwatch_alarms' or 'list_guardduty_findings' which also list AWS resources, leaving some ambiguity about scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, nor does it reference sibling tools that might serve similar monitoring purposes in AWS.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bhaveshopss/MCP-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server