Skip to main content
Glama
aliyun

Alibaba Cloud RDS OpenAPI MCP Server

Official
by aliyun

modify_db_instance_spec

Modify Alibaba Cloud RDS instance specifications including class, storage, and payment type. Choose immediate or scheduled switch for controlled updates.

Instructions

Modify RDS instance specifications.

Args:
    region_id: The region ID of the RDS instance.
    dbinstance_id: The ID of the RDS instance.
    dbinstance_class: Target instance specification.
    dbinstance_storage: Target storage space in GB.
    pay_type: Instance payment type. Values: Postpaid, Prepaid, Serverless.
    effective_time: When the new configuration takes effect. Values: Immediate, MaintainTime, ScheduleTime.
    switch_time: Scheduled switch time in format: yyyy-MM-ddTHH:mm:ssZ (UTC time).
    switch_time_mode: Switch time mode. Values: Immediate, MaintainTime, ScheduleTime.
    source_biz: Source business type.
    dedicated_host_group_id: Dedicated host group ID.
    zone_id: Zone ID.
    vswitch_id: VSwitch ID.
    category: Instance category.
    instance_network_type: Instance network type.
    direction: Specification change direction. Values: UP, DOWN.
    auto_pause: Whether to enable auto pause for Serverless instances.
    max_capacity: Maximum capacity for Serverless instances.
    min_capacity: Minimum capacity for Serverless instances.
    switch_force: Whether to force switch for Serverless instances.
    client_token: Client token for idempotency, max 64 ASCII characters.

Returns:
    Dict[str, Any]: The response containing the request ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zone_idNo
categoryNo
pay_typeNo
directionNo
region_idYes
auto_pauseNo
source_bizNo
vswitch_idNo
switch_timeNo
client_tokenNo
max_capacityNo
min_capacityNo
switch_forceNo
dbinstance_idYes
effective_timeNo
dbinstance_classNo
switch_time_modeNo
dbinstance_storageNo
instance_network_typeNo
dedicated_host_group_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description carries full burden. It only says 'modify' but does not disclose side effects like potential downtime, restart, or data loss. Behavioral traits such as destructive nature are not addressed.

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?

One-line purpose followed by a structured parameter list. No extraneous text. Efficient and front-loaded, though the list is long due to 20 parameters.

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?

With output schema present, return description is minimal but acceptable. However, the description does not explain constraints like whether storage can only be increased, or which parameter combinations are invalid. Overall adequate but with gaps.

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?

Schema description coverage is 0%, so description must add meaning. It provides brief explanations for each parameter (e.g., 'pay_type: Instance payment type. Values: Postpaid, Prepaid, Serverless.'), but some (e.g., 'zone_id: Zone ID') are vague. Adds some value but not comprehensive.

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 'Modify RDS instance specifications,' which clearly states the verb and resource. It distinguishes from sibling tools like create_db_instance (creating) and describe_db_instances (reading).

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?

No guidance on when to use this tool versus alternatives, nor any prerequisites or conditions. For example, it doesn't mention that the RDS instance must exist or must be in a specific state.

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