Skip to main content
Glama
rainhan99

Cloud Manage MCP Server

by rainhan99

reboot_alibaba_instance

Restart an Alibaba Cloud ECS instance with triple confirmation for safety. Use this tool to reboot cloud servers when needed.

Instructions

重启阿里云ECS实例(需要三次确认)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instance_idYes
ip_confirmationNo
name_confirmationNo
operation_confirmationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:599-612 (handler)
    MCP tool handler for 'reboot_alibaba_instance'. Registers the tool and proxies to alibaba_provider.reboot_instance with security confirmation parameters.
    @mcp.tool()
    def reboot_alibaba_instance(
        instance_id: str, 
        ip_confirmation: str = "", 
        name_confirmation: str = "", 
        operation_confirmation: str = ""
    ) -> Dict:
        """
        重启阿里云ECS实例(需要三次确认)
        """
        return alibaba_provider.reboot_instance(
            instance_id, ip_confirmation, name_confirmation, operation_confirmation
        )
  • AlibabaProvider.reboot_instance method: Entry point for reboot logic, delegates to _execute_power_operation with 'reboot' action.
    def reboot_instance(
        self, 
        instance_id: str, 
        ip_confirmation: str = "", 
        name_confirmation: str = "", 
        operation_confirmation: str = ""
    ) -> Dict:
        """
        重启ECS实例(需要三次确认)
        """
        return self._execute_power_operation(
            instance_id, 'reboot', ip_confirmation, name_confirmation, operation_confirmation
        )
  • Core helper implementing power operations (including reboot). Fetches instance details, validates triple confirmation, and executes Alibaba Cloud ECS RebootInstance API call.
    def _execute_power_operation(
        self, 
        instance_id: str, 
        operation: str, 
        ip_confirmation: str, 
        name_confirmation: str, 
        operation_confirmation: str
    ) -> Dict:
        """
        执行电源操作的通用函数
        """
        if not self.available:
            return {
                'error': f'阿里云服务不可用: {getattr(self, "error", "未知错误")}',
                'provider': 'alibaba'
            }
        
        # 首先获取实例信息
        try:
            request = ecs_models.DescribeInstancesRequest(
                region_id=self.region_id,
                instance_ids=json.dumps([instance_id])
            )
            
            response = self.client.describe_instances(request)
            
            if not response.body.instances or not response.body.instances.instance:
                return {
                    'error': f'未找到ID为 {instance_id} 的ECS实例',
                    'provider': 'alibaba'
                }
            
            instance = response.body.instances.instance[0]
            
            # 格式化实例信息用于确认
            instance_info = self._format_instance_for_confirmation(instance)
            
        except Exception as e:
            return {
                'error': f'获取ECS实例信息时发生错误: {str(e)}',
                'provider': 'alibaba'
            }
        
        # 检查是否提供了确认信息
        if not ip_confirmation or not name_confirmation or not operation_confirmation:
            # 转换操作名称
            operation_mapping = {
                'start': 'power_on',
                'stop': 'power_off',
                'reboot': 'reboot'
            }
            mapped_operation = operation_mapping.get(operation, operation)
            return require_triple_confirmation(instance_info, mapped_operation)
        
        # 验证确认信息
        security = SecurityConfirmation()
        operation_mapping = {
            'start': 'power_on',
            'stop': 'power_off',
            'reboot': 'reboot'
        }
        mapped_operation = operation_mapping.get(operation, operation)
        
        is_valid, error_message = security.validate_power_operation(
            instance_info, mapped_operation, ip_confirmation, name_confirmation, operation_confirmation
        )
        
        if not is_valid:
            return {
                'error': f'确认验证失败: {error_message}',
                'provider': 'alibaba',
                'requires_confirmation': True
            }
        
        # 执行实际操作
        try:
            if operation == 'start':
                request = ecs_models.StartInstanceRequest(
                    instance_id=instance_id
                )
                response = self.client.start_instance(request)
            elif operation == 'stop':
                request = ecs_models.StopInstanceRequest(
                    instance_id=instance_id,
                    force_stop=True
                )
                response = self.client.stop_instance(request)
            elif operation == 'reboot':
                request = ecs_models.RebootInstanceRequest(
                    instance_id=instance_id,
                    force_stop=True
                )
                response = self.client.reboot_instance(request)
            else:
                return {
                    'error': f'不支持的操作类型: {operation}',
                    'provider': 'alibaba'
                }
            
            return {
                'provider': 'alibaba',
                'instance_id': instance_id,
                'operation_success': True,
                'operation': operation,
                'request_id': response.body.request_id,
                'message': f'已成功提交 {operation} 操作',
                'confirmation_validated': True
            }
            
        except Exception as e:
            return {
                'error': f'执行 {operation} 操作时发生错误: {str(e)}',
                'provider': 'alibaba'
            }
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 '需要三次确认' (requires three confirmations), which adds some behavioral context about a safety mechanism. However, it doesn't disclose other critical traits like whether this is a destructive operation, what permissions are required, rate limits, or what happens during the reboot process. For a mutation tool with zero annotation coverage, this is insufficient.

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

Conciseness5/5

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

The description is a single, efficient sentence in Chinese that is front-loaded with the core action and resource. There is no wasted text, and it's appropriately sized for the tool's complexity.

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 (a destructive reboot operation with 4 parameters), no annotations, and 0% schema description coverage, the description is incomplete. It lacks details on prerequisites, error conditions, output format (though an output schema exists, the description doesn't reference it), and how to handle the confirmations. For a mutation tool, this is inadequate.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It implies confirmations are needed but doesn't explain the four parameters (instance_id, ip_confirmation, name_confirmation, operation_confirmation) or their purposes. The description adds minimal value beyond the schema, failing to clarify parameter meanings or usage.

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 ('重启' meaning 'reboot') and the resource ('阿里云ECS实例' meaning 'Alibaba Cloud ECS instance'), which is specific and unambiguous. It distinguishes from siblings like 'power_off_alibaba_instance' by focusing on reboot rather than power off/on. However, it doesn't explicitly differentiate from 'manage_instance_power' which might also handle reboots.

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 mentions '需要三次确认' (requires three confirmations), which implies a specific usage context where confirmations are needed, but it doesn't provide explicit guidance on when to use this tool versus alternatives like 'power_off_alibaba_instance' or 'manage_instance_power'. No alternatives or exclusions are mentioned.

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/rainhan99/cloud_manage_mcp_server'

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