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 and database engine.

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
region_idYes
engineYes
engine_versionNo
commodity_codeNo
zone_idNo
dispense_modeNo
dbinstance_nameNo
categoryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description's 'Query' aligns. No additional behavioral traits are disclosed beyond the obvious read operation, which is acceptable given the annotations.

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 structured with a clear purpose, parameter list, and return type. It is reasonably concise given the 8 parameters, though some examples could be streamlined.

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

Completeness5/5

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

All 8 parameters are thoroughly explained, and the output schema exists (though not shown). The description covers everything needed for an agent to invoke the tool correctly.

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?

Schema description coverage is 0%, but the description includes a detailed docstring for each parameter with examples, meanings, and defaults. This fully compensates for the lack of schema descriptions.

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 it 'Query available zones for RDS instances', using a specific verb and resource. It distinguishes from siblings like 'describe_available_classes' by focusing on zones.

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 the function signature and parameter explanations but does not explicitly state when to use this tool versus alternatives or exclude scenarios. It implies usage context for querying zones.

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