Skip to main content
Glama

rds-describe_db_instances

Retrieve detailed information about AWS RDS database instances for monitoring, auditing, and management purposes with advanced filtering capabilities.

Instructions

Retrieve comprehensive RDS database instance information with advanced filtering and pagination.

This tool provides detailed information about RDS database instances including configuration,
status, performance settings, and security details. Essential for database monitoring,
compliance auditing, and operational management.

**Required Parameters:**
- profile_name (str): AWS profile name from ~/.aws/credentials
- region (str): AWS region (e.g., 'us-east-1', 'eu-west-1')

**Optional Parameters:**
- db_instance_identifier (str): Specific database instance identifier
  Example: 'production-mysql-db', 'staging-postgres-01'

- filters (Dict[str, Any]): Advanced filtering options
  **Engine Filters:**
  - 'engine': Database engine types
    * MySQL: ['mysql']
    * PostgreSQL: ['postgres']
    * Oracle: ['oracle-ee', 'oracle-se2', 'oracle-se1', 'oracle-se']
    * SQL Server: ['sqlserver-ex', 'sqlserver-web', 'sqlserver-se', 'sqlserver-ee']
    * MariaDB: ['mariadb']
    * Aurora: ['aurora-mysql', 'aurora-postgresql']

  **Version Filters:**
  - 'engine-version': ['8.0.35', '13.7', '19.0.0.0.ru-2023-01.rur-2023-01.r1']

  **Instance Class Filters:**
  - 'db-instance-class': ['db.t3.micro', 'db.r5.large', 'db.m5.xlarge']

  **Status Filters:**
  - 'db-instance-status': ['available', 'creating', 'deleting', 'modifying', 'rebooting', 'stopped']

  **Network Filters:**
  - 'vpc-id': ['vpc-12345678'] - Filter by VPC
  - 'subnet-group-name': ['default', 'custom-subnet-group']

  **Availability Filters:**
  - 'availability-zone': ['us-east-1a', 'us-east-1b']
  - 'multi-az': ['true', 'false'] - Multi-AZ deployment filter

  **Security Filters:**
  - 'db-security-group': ['sg-12345678'] - VPC security groups
  - 'db-parameter-group': ['default.mysql8.0', 'custom-params']

  **Backup and Maintenance:**
  - 'backup-retention-period': ['7', '14', '30'] - Backup retention days
  - 'maintenance-window': ['sun:05:00-sun:06:00'] - Maintenance window

  **Performance Insights:**
  - 'performance-insights-enabled': ['true', 'false']
  - 'monitoring-interval': ['0', '60', '300'] - Enhanced monitoring interval

- max_records (int): Maximum results per request (20-100)
  * Default: 100
  * Use smaller values for memory efficiency
  * Combine with pagination for large fleets

- marker (str): Pagination marker from previous response
  * Use 'Marker' value from previous call
  * Enables seamless pagination through large DB fleets

**Common Use Cases:**
1. **Production DB audit:** filters={'engine': ['mysql'], 'db-instance-status': ['available']}
2. **Multi-AZ check:** filters={'multi-az': ['true']}
3. **Security audit:** filters={'vpc-id': ['vpc-12345678']}
4. **Performance monitoring:** filters={'performance-insights-enabled': ['true']}
5. **Backup compliance:** filters={'backup-retention-period': ['7', '14', '30']}
6. **Engine version check:** filters={'engine': ['mysql'], 'engine-version': ['8.0.35']}

**Response includes:** DB instance identifier, status, engine details, instance class,
availability zone, VPC security groups, parameter groups, backup settings, performance
insights status, monitoring configuration, endpoint information, and more.

**Use Cases:**
- Database inventory and compliance reporting
- Performance monitoring and optimization
- Security auditing and configuration review
- Backup and disaster recovery planning
- Cost optimization and rightsizing analysis

Essential for comprehensive RDS fleet management and operational visibility.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profile_nameYes
regionYes
db_instance_identifierNo
filtersNo
max_recordsNo
markerNo
Behavior4/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 effectively describes the tool's behavior: it's a read operation (implied by 'retrieve'), supports pagination (via 'marker' parameter), has filtering capabilities, and returns comprehensive instance data. It also mentions memory efficiency considerations for 'max_records'. While it doesn't cover rate limits or authentication details beyond profile/region parameters, it provides substantial behavioral context for a read operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While well-structured with clear sections (purpose, parameters, use cases), the description is verbose with redundant sections ('Common Use Cases' and 'Use Cases' repeat similar information). Some sentences don't earn their place, such as the final 'Essential for comprehensive RDS fleet management and operational visibility' which restates earlier points. The front-loading is good, but overall length could be reduced without losing value.

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?

For a 6-parameter tool with no annotations and no output schema, the description provides substantial context. It explains what the tool does, how to use parameters, and what information is returned ('Response includes: DB instance identifier, status, engine details...'). The main gap is the lack of output schema, but the description compensates by listing return data categories. Given the complexity, it's nearly complete but could benefit from explicit error handling or rate limit information.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Given 0% schema description coverage, the description compensates fully by providing detailed semantic information for all 6 parameters. It clearly distinguishes required vs. optional parameters, provides examples (e.g., region: 'us-east-1'), explains complex nested structures (the 'filters' dictionary with 12 sub-filters and their allowed values), and gives practical guidance on parameter usage (e.g., 'Use smaller values for memory efficiency' for max_records).

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

Purpose5/5

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

The description clearly states the tool's purpose: 'Retrieve comprehensive RDS database instance information with advanced filtering and pagination.' It specifies the verb ('retrieve'), resource ('RDS database instance information'), and distinguishes it from siblings by focusing on RDS instances rather than EC2, S3, or CloudWatch resources mentioned in the sibling list.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('Essential for database monitoring, compliance auditing, and operational management') and includes six specific use cases with filter examples. However, it doesn't explicitly state when NOT to use it or name alternatives among sibling tools for related AWS operations.

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/Havoc24k/aws-sa-tools-mcp-server'

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