Skip to main content
Glama
aliyun

Alibaba Cloud RDS OpenAPI MCP Server

Official
by aliyun

describe_available_classes

Read-only

Check which RDS instance classes and storage sizes are available for purchase in a specific region and zone, based on engine, version, and payment type.

Instructions

Query the RDS instance class_code and storage space that can be purchased in the inventory.

Args:
    region_id: The region ID of the RDS instance.
    zone_id: The zone ID of the RDS instance. Query available zones by `describe_available_zones`.
    instance_charge_type: Instance payment type. Values: Prepaid, Postpaid, Serverless.
    engine: Database engine type. Values: MySQL, SQLServer, PostgreSQL, MariaDB.
    engine_version: Database version.
    dbinstance_storage_type: Storage type. Values: local_ssd,general_essd,cloud_essd,cloud_essd2,cloud_essd3
    category: Instance category. Values: Basic, HighAvailability, cluster, AlwaysOn, Finance, serverless_basic, serverless_standard, serverless_ha.
    dbinstance_id: The ID of the RDS instance.
    order_type: Order type. Currently only supports "BUY".
    commodity_code: Commodity code for read-only instances.

Returns:
    Dict[str, Any]: The response containing available instance classes and storage ranges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
engineYes
zone_idYes
categoryYes
region_idYes
order_typeNo
dbinstance_idNo
commodity_codeNo
engine_versionYes
instance_charge_typeYes
dbinstance_storage_typeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description's 'Query' aligns with that. The description adds context by specifying the return type and parameter roles, but does not elaborate on potential side effects or rate limits, which is acceptable for a read-only tool.

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 Args and Returns sections and is front-loaded with the purpose. While concise overall, it could be slightly shortened without losing clarity, but every sentence is informative.

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's complexity (10 parameters, 7 required) and lack of output schema, the description covers all parameters and mentions the return type (Dict[str, Any]) and content (instance classes and storage ranges). It is sufficiently complete for a query tool.

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 fully compensates by listing each parameter, its purpose, and acceptable values (e.g., engine: MySQL, SQLServer, etc.). This adds critical meaning beyond the raw schema types.

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 'Query the RDS instance class_code and storage space that can be purchased in the inventory', providing a specific verb and resource. It distinguishes itself from siblings like describe_available_zones by focusing on class_code and storage, not 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 implicitly indicates usage when needing available instance classes and storage, and mentions a related tool (describe_available_zones) for zone queries. However, it lacks explicit when-not-to-use or alternative tools for other scenarios.

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