Skip to main content
Glama
aliyun

Alibaba Cloud RDS OpenAPI MCP Server

Official
by aliyun
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

describe_available_zones

Read-only

Query available zones for Alibaba Cloud RDS instances by specifying region, engine, and optional filters.

Instructions

Query available zones for RDS instances.

Args:
    region_id: Region ID.
    engine: Database type (MySQL, SQLServer, PostgreSQL, MariaDB).
    engine_version: Database version.
        MySQL: 5.5, 5.6, 5.7, 8.0
        SQL Server: 2008r2, 2012, 2014, 2016, 2017, 2019
        PostgreSQL: 10.0, 11.0, 12.0, 13.0, 14.0, 15.0
        MariaDB: 10.3
    commodity_code: Commodity code.
        bards: Pay-as-you-go primary instance (China site)
        rds: Subscription primary instance (China site)
        rords: Pay-as-you-go read-only instance (China site)
        rds_rordspre_public_cn: Subscription read-only instance (China site)
        bards_intl: Pay-as-you-go primary instance (International site)
        rds_intl: Subscription primary instance (International site)
        rords_intl: Pay-as-you-go read-only instance (International site)
        rds_rordspre_public_intl: Subscription read-only instance (International site)
        rds_serverless_public_cn: Serverless instance (China site)
        rds_serverless_public_intl: Serverless instance (International site)
    zone_id: Zone ID.
    dispense_mode: Whether to return zones that support single-zone deployment.
        1: Return (default)
        0: Do not return
    dbinstance_name: Primary instance ID. Required when querying read-only instance resources.
    category: Instance category.
        Basic: Basic Edition
        HighAvailability: High-availability Edition
        cluster: MySQL Cluster Edition
        AlwaysOn: SQL Server Cluster Edition
        Finance: Enterprise Edition
        serverless_basic: Serverless Basic Edition
        serverless_standard: MySQL Serverless High-availability Edition
        serverless_ha: SQL Server Serverless High-availability Edition

Returns:
    Dict[str, Any]: Response containing available zones information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
engineYes
zone_idNo
categoryNo
region_idYes
dispense_modeNo
commodity_codeNo
engine_versionNo
dbinstance_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A3.8/5.0
Behavior3/5

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

The readOnlyHint annotation already indicates no side effects. The description adds some behavioral context through parameter options (e.g., dispense_mode, category) but does not disclose potential rate limits, authentication needs, or return format details beyond 'Dict[str, Any].'

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

Conciseness4/5

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

The description is well-structured with an Args list and Returns section, making it easy to scan. However, it is somewhat verbose, particularly the full lists of engine versions and commodity codes, which could be abbreviated.

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 8 parameters with no schema descriptions and an output schema exists (though not shown), the description provides essential parameter semantics and a return type hint. It lacks details on error handling, pagination, or limits, but for a read-only zone query, it is reasonably complete.

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?

With 0% schema description coverage, the description compensates fully by enumerating allowed values for engine_version, commodity_code, dispense_mode, category, and explaining the purpose of each parameter, including defaults and dependencies (e.g., dbinstance_name required for read-only instances).

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 'Query available zones for RDS instances,' specifying the verb and resource. However, it does not explicitly differentiate from sibling tools like 'describe_available_classes,' which serves a similar query purpose for instance classes.

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

Usage Guidelines3/5

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

The description implies usage for checking available zones when configuring RDS instances through the parameter list, but it lacks explicit guidance on when to use this tool versus alternatives, nor does it state prerequisites or exclusions.

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