Skip to main content
Glama
code-alchemist01

MCP Cloud Services Server

list_alarms

Retrieve monitoring alarms across AWS, Azure, or GCP cloud services to track system alerts and performance issues.

Instructions

List monitoring alarms

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
providerYesCloud provider
resourceIdNoResource ID (optional)

Implementation Reference

  • Handler logic for the 'list_alarms' tool within the handleMonitoringTool switch statement. Currently a stub implementation that returns a message indicating it is not fully implemented.
    case 'list_alarms': {
      return { message: `Alarm listing not yet fully implemented for ${provider}` };
    }
  • Tool definition for 'list_alarms' including name, description, and input schema for validation.
    {
      name: 'list_alarms',
      description: 'List monitoring alarms',
      inputSchema: {
        type: 'object',
        properties: {
          provider: {
            type: 'string',
            enum: ['aws', 'azure', 'gcp'],
            description: 'Cloud provider',
          },
          resourceId: {
            type: 'string',
            description: 'Resource ID (optional)',
          },
        },
        required: ['provider'],
      },
    },
  • Registration of 'list_alarms' tool as part of the exported monitoringTools array.
    export const monitoringTools: Tool[] = [
      {
        name: 'get_metrics',
        description: 'Get metrics for a cloud resource',
        inputSchema: {
          type: 'object',
          properties: {
            provider: {
              type: 'string',
              enum: ['aws', 'azure', 'gcp'],
              description: 'Cloud provider',
            },
            resourceId: {
              type: 'string',
              description: 'Resource ID',
            },
            metricName: {
              type: 'string',
              description: 'Metric name (e.g., CPUUtilization, NetworkIn)',
            },
            startTime: {
              type: 'string',
              description: 'Start time (ISO 8601)',
            },
            endTime: {
              type: 'string',
              description: 'End time (ISO 8601)',
            },
            period: {
              type: 'number',
              description: 'Period in seconds',
              default: 3600,
            },
          },
          required: ['provider', 'resourceId', 'metricName', 'startTime', 'endTime'],
        },
      },
      {
        name: 'list_alarms',
        description: 'List monitoring alarms',
        inputSchema: {
          type: 'object',
          properties: {
            provider: {
              type: 'string',
              enum: ['aws', 'azure', 'gcp'],
              description: 'Cloud provider',
            },
            resourceId: {
              type: 'string',
              description: 'Resource ID (optional)',
            },
          },
          required: ['provider'],
        },
      },
      {
        name: 'get_resource_health',
        description: 'Get health status of a cloud resource',
        inputSchema: {
          type: 'object',
          properties: {
            provider: {
              type: 'string',
              enum: ['aws', 'azure', 'gcp'],
              description: 'Cloud provider',
            },
            resourceId: {
              type: 'string',
              description: 'Resource ID',
            },
            resourceType: {
              type: 'string',
              enum: ['instance', 'storage', 'database', 'function'],
              description: 'Resource type',
            },
          },
          required: ['provider', 'resourceId', 'resourceType'],
        },
      },
    ];
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('List') without detailing what the list includes (e.g., alarm states, severities), how results are returned (e.g., pagination, sorting), or any constraints like rate limits or authentication needs. This is inadequate for a tool with potential complexity in cloud monitoring.

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 extremely concise with just three words, front-loaded with the core action. There is zero waste or redundancy, making it easy to parse quickly, though this conciseness comes at the cost of detail in other dimensions.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of cloud monitoring alarms and the lack of annotations and output schema, the description is incomplete. It doesn't explain what information is returned (e.g., alarm names, statuses, timestamps) or behavioral aspects like error handling. For a tool that likely interacts with multiple cloud providers, more context is needed to guide effective use.

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?

The input schema has 100% description coverage, with clear documentation for both parameters (provider and resourceId). The description adds no additional meaning beyond what the schema provides, such as explaining how resourceId filters alarms or the implications of provider choice. Baseline score of 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List monitoring alarms' clearly states the verb ('List') and resource ('monitoring alarms'), but it's vague about scope and doesn't differentiate from sibling tools like 'get_metrics' or 'get_resource_health' that might also relate to monitoring. It specifies the type of alarms but lacks detail about what constitutes a 'monitoring alarm' in this context.

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 sibling tools like 'list_resources' or context-specific tools (e.g., 'aws_list_ec2_instances'), nor does it specify prerequisites or exclusions, leaving the agent to infer usage based on the name alone.

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/code-alchemist01/Cloud-mcp_server'

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