Skip to main content
Glama
aliyun

Alibaba Cloud RDS OpenAPI MCP Server

Official
by aliyun

modify_db_instance_spec

Modify RDS instance specifications such as class, storage, and pay type to scale resources or change configuration.

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
region_idYes
dbinstance_idYes
dbinstance_classNo
dbinstance_storageNo
pay_typeNo
effective_timeNo
switch_timeNo
switch_time_modeNo
source_bizNo
dedicated_host_group_idNo
zone_idNo
vswitch_idNo
categoryNo
instance_network_typeNo
directionNo
auto_pauseNo
max_capacityNo
min_capacityNo
switch_forceNo
client_tokenNo

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 carries the full burden. It mentions 'Modify' implying mutation but lacks details on idempotency, rate limits, auth requirements, or side effects. The return type is minimally described as 'Dict[str, Any]'.

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 the main action is front-loaded. However, it is somewhat lengthy due to detailed parameter explanations, which is acceptable given the parameter count. Every sentence serves a purpose.

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?

Given 20 parameters, no annotations, and an output schema that exists but not detailed, the description falls short. It explains all parameters but does not cover behavioral context, error handling, or a comprehensive return value specification. The return is only 'request ID'.

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%, meaning the schema only has titles. The description compensates fully by providing detailed explanations, accepted values, and formatting for each of the 20 parameters (e.g., pay_type: 'Values: Postpaid, Prepaid, Serverless'). This adds significant meaning beyond the schema.

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 modifies RDS instance specifications, with a specific verb and resource. It distinguishes itself from sibling tools like modify_db_instance_description and modify_security_ips by focusing on specs.

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 vs alternatives. The description simply lists parameters without providing context on prerequisites, exclusions, or typical scenarios. An agent would need to infer usage from the tool name and parameters.

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