Skip to main content
Glama
code-alchemist01

MCP Cloud Services Server

aws_list_rds_instances

List all AWS RDS database instances in a specified region to manage cloud resources and monitor database deployments.

Instructions

List all RDS database instances in AWS

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNoAWS regionus-east-1

Implementation Reference

  • Core handler implementing AWS RDS instance listing using RDSClient and DescribeDBInstancesCommand, mapping results to RDSInstance format.
    async listRDSInstances(): Promise<RDSInstance[]> {
      await this.initializeClients();
      if (!this.rdsClient) throw new Error('RDS client not initialized');
    
      try {
        const command = new DescribeDBInstancesCommand({});
        const response = await this.rdsClient.send(command);
    
        const instances: RDSInstance[] = [];
    
        for (const dbInstance of response.DBInstances || []) {
          instances.push({
            id: dbInstance.DBInstanceIdentifier || '',
            type: 'database',
            name: dbInstance.DBInstanceIdentifier || '',
            region: this.region,
            status: this.mapDBInstanceState(dbInstance.DBInstanceStatus),
            dbInstanceIdentifier: dbInstance.DBInstanceIdentifier || '',
            engine: dbInstance.Engine || '',
            engineVersion: dbInstance.EngineVersion || '',
            instanceClass: dbInstance.DBInstanceClass || '',
            allocatedStorage: dbInstance.AllocatedStorage,
            multiAZ: dbInstance.MultiAZ,
          });
        }
    
        return instances;
      } catch (error) {
        throw new Error(`Failed to list RDS instances: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • Tool handler case within handleAWSTool that calls AWSAdapter.listRDSInstances() and formats output for the tool response.
    case 'aws_list_rds_instances': {
      const instances = await adapter.listRDSInstances();
      return {
        total: instances.length,
        instances: instances.map((inst) => ({
          id: inst.id,
          name: inst.dbInstanceIdentifier,
          engine: inst.engine,
          engineVersion: inst.engineVersion,
          instanceClass: inst.instanceClass,
          status: inst.status,
          region: inst.region,
        })),
      };
    }
  • Tool schema definition including name, description, and inputSchema with optional region parameter.
    {
      name: 'aws_list_rds_instances',
      description: 'List all RDS database instances in AWS',
      inputSchema: {
        type: 'object',
        properties: {
          region: {
            type: 'string',
            description: 'AWS region',
            default: 'us-east-1',
          },
        },
      },
    },
  • src/server.ts:19-27 (registration)
    MCP tool registration: includes awsTools (containing aws_list_rds_instances) in the allTools array returned by listTools handler.
    const allTools = [
      ...awsTools,
      ...azureTools,
      ...gcpTools,
      ...resourceManagementTools,
      ...costAnalysisTools,
      ...monitoringTools,
      ...securityTools,
    ];
  • src/server.ts:64-65 (registration)
    MCP server routes calls to aws_list_rds_instances by checking against awsTools and invoking handleAWSTool.
    if (awsTools.some((t) => t.name === name)) {
      result = await handleAWSTool(name, args || {});
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it's a list operation, implying read-only behavior, but doesn't cover important aspects like authentication requirements, rate limits, pagination, or what data is returned. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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 that directly states the tool's purpose with no wasted words. It's appropriately sized for a simple list tool and front-loaded with the essential 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?

For a simple list tool with one well-documented parameter and no output schema, the description is minimally adequate. However, with no annotations and siblings that could cause confusion, it lacks completeness in guiding usage and understanding behavioral traits. It covers the basic 'what' but not the 'how' or 'when'.

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 the single parameter 'region' clearly documented as 'AWS region' with a default value. The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline for high schema coverage without compensating value.

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 ('List') and resource ('all RDS database instances in AWS'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'aws_list_ec2_instances' or 'list_resources', but it's specific enough to identify the exact AWS service and resource type.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'aws_list_ec2_instances', 'list_resources', and 'get_resource', the description doesn't help an agent choose between them for listing RDS instances specifically. There's no mention of prerequisites or context for usage.

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