Skip to main content
Glama
aliyun

Alibaba Cloud RDS OpenAPI MCP Server

Official
by aliyun

create_db_instance

Provision an Alibaba Cloud RDS instance by specifying engine, version, class, storage, and network settings.

Instructions

Create an RDS instance.

Args:
    region_id: Region ID.
    engine: Database type (MySQL, SQLServer, PostgreSQL, MariaDB).
    engine_version: Database version.
    dbinstance_class: Instance specification. Query available class_codes by `describe_available_classes`.
    dbinstance_storage: Storage space in GB.
    security_ip_list: IP whitelist, separated by commas. Default: "127.0.0.1".
    instance_network_type: Network type (Classic, VPC). Default: VPC.
    zone_id: Zone ID. Query available zones by `describe_available_zones`.
    zone_id_slave1: Slave Node1 Zone ID. Query available zones by `describe_available_zones`.
    zone_id_slave2: Slave Node2 Zone ID. Query available zones by `describe_available_zones`.
    pay_type: Payment type (Postpaid, Prepaid). Default: Postpaid.
    instance_charge_type: Instance charge type.
    system_db_charset: Character set.
    dbinstance_net_type: Network connection type (Internet, Intranet). Default: Internet.
    category: Instance category. Default: Basic.
    dbinstance_storage_type: Storage type. (e.g. local_ssd,general_essd,cloud_essd,cloud_essd2,cloud_essd3)
    vpc_id: VPC ID.
    vswitch_id: VSwitch ID.
    private_ip_address: Private IP address.
    client_token: Idempotence token.
    resource_group_id: Resource group ID.
    tde_status: TDE status (Enable, Disable).
    encryption_key: Custom encryption key.
    serverless_config: Serverless instance configuration.
    table_names_case_sensitive: Are table names case-sensitive.
    db_time_zone: the db instance time zone.
    connection_string: the connection string for db instance.
    db_param_group_id: the db param group id for db instance.
Returns:
    Dict[str, Any]: Response containing the created instance details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
engineYes
vpc_idYes
zone_idYes
categoryNoBasic
pay_typeNoPostpaid
region_idYes
tde_statusNo
vswitch_idYes
client_tokenNo
db_time_zoneNo
encryption_keyNo
engine_versionYes
zone_id_slave1No
zone_id_slave2No
dbinstance_classYes
security_ip_listNo127.0.0.1
connection_stringNo
db_param_group_idNo
resource_group_idNo
serverless_configNo
system_db_charsetNo
dbinstance_storageYes
private_ip_addressNo
dbinstance_net_typeNoInternet
instance_network_typeNoVPC
dbinstance_storage_typeNo
table_names_case_sensitiveNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions 'Create' implying mutation and includes a client_token for idempotency, but does not discuss permissions, asynchronous behavior, or side effects beyond creation. This is insufficient for a complex provisioning tool.

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?

The description follows a standard docstring format with Args and Returns sections. It is systematic but verbose due to listing all parameters. The first line directly states the purpose, which is good, but the bulk could be trimmed or organized more efficiently.

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

Completeness3/5

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

All parameters are covered, and there are hints about prerequisites (e.g., VPC, VSwitch are required). However, preconditions like existing network resources are not explicitly stated, and the return value is merely 'Dict[str, Any]' without detail. Given the tool's complexity, more completeness is needed.

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?

The description adds meaning to all 27 parameters beyond the schema's bare type/name/default (since schema description coverage is 0%). It provides brief descriptions, defaults, and references to sibling tools for queries (e.g., 'Query available class_codes by describe_available_classes'). Some descriptions are terse but still valuable.

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 starts with 'Create an RDS instance,' which clearly states the tool's verb and resource. The sibling tools are primarily describe and modify operations, so this creation tool is distinct and well-positioned.

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 does not explicitly state when to use this tool versus alternatives. It indirectly references sibling tools (describe_available_classes, describe_available_zones) in parameter descriptions, but lacks direct guidance on when to create vs. describe or modify.

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