Skip to main content
Glama
aliyun

Alibaba Cloud RDS OpenAPI MCP Server

Official
by aliyun

create_db_instance

Create a new RDS database instance on Alibaba Cloud 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
region_idYes
engineYes
engine_versionYes
dbinstance_classYes
dbinstance_storageYes
vpc_idYes
vswitch_idYes
zone_idYes
zone_id_slave1No
zone_id_slave2No
security_ip_listNo127.0.0.1
instance_network_typeNoVPC
pay_typeNoPostpaid
system_db_charsetNo
dbinstance_net_typeNoInternet
categoryNoBasic
dbinstance_storage_typeNo
private_ip_addressNo
client_tokenNo
resource_group_idNo
tde_statusNo
encryption_keyNo
serverless_configNo
table_names_case_sensitiveNo
db_time_zoneNo
connection_stringNo
db_param_group_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It mentions mutation ('Create') and hints at idempotency via 'client_token', but does not describe side effects, permissions, rate limits, or reversibility. The lack of safety information is a significant gap for a resource creation tool.

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

Conciseness2/5

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

The description is verbose with a long list of parameters, many of which have minimal explanations. It lacks grouping (required vs optional) and uses repetitive phrasing. The opening sentence is clear, but the bulk is unstructured and not concise.

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

Completeness2/5

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

While the description covers parameter documentation, it omits behavioral context (e.g., required permissions, side effects, availability zones) and provides a vague return type ('Dict[str, Any]'). For a complex creation tool with 27 parameters, more completeness is needed for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds value beyond schema titles for several parameters (e.g., querying available classes, default values, example storage types). However, many parameter explanations are trivial (e.g., 'Resource group ID') and do not provide deeper meaning. Given 0% schema description coverage, the description partially compensates but leaves gaps.

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 creates an RDS instance, with a specific verb ('Create') and resource ('RDS instance'). It distinguishes from siblings like describe_available_classes and describe_available_zones by being a creation action.

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 useful context by referencing sibling tools (describe_available_classes, describe_available_zones) for prerequisite queries, but lacks explicit when-to-use or when-not-to-use guidance. It does not mention alternatives for similar tasks.

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