Skip to main content
Glama
aliyun

Alibaba Cloud RDS OpenAPI MCP Server

Official
by aliyun

describe_db_instance_databases

Read-only

Retrieve database details for multiple Alibaba Cloud RDS instances in a single batch operation to monitor and manage database configurations.

Instructions

Batch retrieves database information for multiple RDS instances.
Args:
    region_id: The region ID of the RDS instance.
    db_instance_ids: List of DB instance identifiers (e.g., ["rm-uf6wjk5****", "db-instance-01"])
Returns:
    list[dict]: A list of dictionaries containing database information for each instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
region_idYes
db_instance_idsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function implementing the 'describe_db_instance_databases' tool. It takes region_id and a list of db_instance_ids, calls the Alibaba Cloud RDS SDK's DescribeDatabases API in a loop for each instance, and returns a list of responses with database info for each.
    @mcp.tool(annotations=READ_ONLY_TOOL)
    async def describe_db_instance_databases(
            region_id: str,
            db_instance_ids: list[str]
    ) -> list[dict]:
        """
        Batch retrieves database information for multiple RDS instances.
        Args:
            region_id: The region ID of the RDS instance.
            db_instance_ids: List of DB instance identifiers (e.g., ["rm-uf6wjk5****", "db-instance-01"])
        Returns:
            list[dict]: A list of dictionaries containing database information for each instance.
        """
        try:
            client = get_rds_client(region_id)
            db_instance_databases = []
            for db_instance_id in db_instance_ids:
                request = rds_20140815_models.DescribeDatabasesRequest(
                    dbinstance_id=db_instance_id
                )
                response = await client.describe_databases_async(request)
                db_instance_databases.append(response.body.to_map())
            return db_instance_databases
        except Exception as e:
            raise e
Behavior3/5

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

The annotations already declare readOnlyHint=true, indicating this is a safe read operation. The description adds some behavioral context by specifying it's a 'batch' operation for 'multiple RDS instances', which helps clarify scope. However, it doesn't provide additional details like rate limits, authentication requirements, or error handling that would be valuable beyond the annotation.

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 well-structured and efficiently organized with clear sections for Args and Returns. Each sentence serves a specific purpose: stating the tool's function, explaining parameters, and describing the return value. There's no wasted text or redundancy.

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?

Given the tool has annotations (readOnlyHint) and an output schema (implied by the Returns section), the description provides adequate context. It explains the tool's batch nature, documents both parameters meaningfully, and describes the return format. However, it could better address when to use this versus similar sibling tools for more complete context.

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?

With 0% schema description coverage, the description carries the full burden of explaining parameters. It successfully clarifies both parameters: 'region_id' as 'The region ID of the RDS instance' and 'db_instance_ids' as 'List of DB instance identifiers' with an example. This adds meaningful context beyond the bare schema, though it could provide more detail about format requirements.

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 tool's purpose with a specific verb ('Batch retrieves') and resource ('database information for multiple RDS instances'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate itself from sibling tools like 'describe_db_instances' or 'describe_db_instance_attribute', which appear to be related but potentially serve different purposes.

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. With many sibling tools like 'describe_db_instances' and 'describe_db_instance_attribute' that seem related, there's no indication of what distinguishes this tool's functionality or when it should be preferred over others.

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/aliyun/alibabacloud-rds-openapi-mcp-server'

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