Skip to main content
Glama
aliyun

AlibabaCloud MCP Server

Official
by aliyun

StartRDSInstances

Start multiple AlibabaCloud RDS instances simultaneously for efficient management during application deployment or high-availability scenarios.

Instructions

批量启动RDS实例,适用于需要同时管理和启动多台RDS实例的场景,例如应用部署和高可用性场景。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
InstanceIdsYesAlibabaCloud ECS instance ID List
RegionIdNoAlibabaCloud region IDcn-hangzhou

Implementation Reference

  • The handler function OOS_StartRDSInstances starts multiple Alibaba Cloud RDS instances using the OOS template 'ACS-RDS-BulkyStartInstances'. It defines the input schema via Pydantic Fields and calls the helper _start_execution_sync.
    @tools.append
    def OOS_StartRDSInstances(
        InstanceIds: List[str] = Field(description='AlibabaCloud ECS instance ID List'),
        RegionId: str = Field(description='AlibabaCloud region ID', default='cn-hangzhou')
    ):
        """批量启动RDS实例,适用于需要同时管理和启动多台RDS实例的场景,例如应用部署和高可用性场景。"""
    
        parameters = {
            'regionId': RegionId,
            'resourceType': 'ALIYUN::RDS::Instance',
            'targets': {
                'ResourceIds': InstanceIds,
                'RegionId': RegionId,
                'Type': 'ResourceIds'
            }
        }
        return _start_execution_sync(region_id=RegionId, template_name='ACS-RDS-BulkyStartInstances', parameters=parameters)
  • Helper function that synchronously starts an OOS execution by polling its status until completion or failure. Used by OOS_StartRDSInstances and other OOS tools.
    def _start_execution_sync(region_id: str, template_name: str, parameters: dict):
        client = create_client(region_id=region_id)
        start_execution_request = oos_20190601_models.StartExecutionRequest(
            region_id=region_id,
            template_name=template_name,
            parameters=json.dumps(parameters)
        )
        start_execution_resp = client.start_execution(start_execution_request)
        execution_id = start_execution_resp.body.execution.execution_id
    
        while True:
            list_executions_request = oos_20190601_models.ListExecutionsRequest(
                region_id=region_id,
                execution_id=execution_id
            )
            list_executions_resp = client.list_executions(list_executions_request)
            status = list_executions_resp.body.executions[0].status
            if status == FAILED:
                status_message = list_executions_resp.body.executions[0].status_message
                raise exception.OOSExecutionFailed(reason=status_message)
            elif status in END_STATUSES:
                return list_executions_resp.body
            time.sleep(1)
    @tools.append
  • Registers all tools from oos_tools (including OOS_StartRDSInstances) to the FastMCP server.
    for tool in oos_tools.tools:
        mcp.tool(tool)
  • Imports the oos_tools module containing the OOS_StartRDSInstances tool.
    from alibaba_cloud_ops_mcp_server.tools import cms_tools, oos_tools, oss_tools, api_tools, common_api_tools
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions batch operations and use cases but fails to disclose critical behavioral traits such as permissions required, whether this is a destructive/mutative operation (implied by 'start' but not explicit), potential side effects, rate limits, or what happens if instances are already running. This leaves significant gaps for an agent to understand the tool's behavior.

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 concise with two sentences that efficiently convey purpose and usage context without unnecessary elaboration. It is front-loaded with the core action and resource, followed by contextual examples. There's minimal waste, though it could be slightly more structured with explicit bullet points for use cases.

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?

Given the tool's complexity (batch operation on cloud resources), lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral risks, output format, error conditions, or prerequisites like authentication. For a mutative tool with no structured safety hints, this leaves the agent under-informed about critical operational aspects.

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 100%, providing good documentation for both parameters (InstanceIds and RegionId). The description adds no additional parameter semantics beyond what's in the schema, such as format details for InstanceIds or RegionId constraints. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('批量启动' - batch start) and resource ('RDS实例' - RDS instances), making the purpose evident. It distinguishes from sibling tools like 'StartInstances' by specifying RDS instances, though it doesn't explicitly contrast with 'StopRDSInstances' or other RDS operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides usage context ('适用于需要同时管理和启动多台RDS实例的场景,例如应用部署和高可用性场景' - suitable for scenarios requiring simultaneous management and startup of multiple RDS instances, such as application deployment and high availability scenarios), which implies when to use it. However, it lacks explicit guidance on when NOT to use it or alternatives like 'StartInstances' for non-RDS instances.

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

Related 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/alibaba-cloud-ops-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server