Skip to main content
Glama
rainhan99

Cloud Manage MCP Server

by rainhan99

reboot_vultr_instance

Restart a Vultr cloud instance with triple confirmation for safety, ensuring controlled server management through the Cloud Manage MCP Server.

Instructions

重启Vultr实例(需要三次确认)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instance_idYes
ip_confirmationNo
name_confirmationNo
operation_confirmationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:527-539 (handler)
    MCP tool handler and registration for 'reboot_vultr_instance'. This function defines the tool interface, input schema via type hints, and delegates to the Vultr provider's reboot_instance method with security confirmation parameters.
    def reboot_vultr_instance(
        instance_id: str, 
        ip_confirmation: str = "", 
        name_confirmation: str = "", 
        operation_confirmation: str = ""
    ) -> Dict:
        """
        重启Vultr实例(需要三次确认)
        """
        return vultr_provider.reboot_instance(
            instance_id, ip_confirmation, name_confirmation, operation_confirmation
        )
  • VultrProvider.reboot_instance method: wrapper that calls the shared _execute_power_operation with 'reboot' action, handling input parameters for security checks.
    def reboot_instance(
        self, 
        instance_id: str, 
        ip_confirmation: str = "", 
        name_confirmation: str = "", 
        operation_confirmation: str = ""
    ) -> Dict:
        """
        重启Vultr实例(需要三次确认)
        """
        return self._execute_power_operation(
            instance_id, 'reboot', ip_confirmation, name_confirmation, operation_confirmation
        )
  • Core handler logic for all Vultr power operations (including reboot). Fetches instance info, enforces triple confirmation security via utils.security, validates inputs, and executes the API call to Vultr's instances/{id}/actions endpoint.
    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'Vultr服务不可用: {getattr(self, "error", "未知错误")}',
                'provider': 'vultr'
            }
        
        # 首先获取实例信息
        try:
            response = requests.get(f'{self.base_url}/instances/{instance_id}', headers=self.headers, timeout=10)
            
            if response.status_code == 404:
                return {
                    'error': f'未找到ID为 {instance_id} 的Vultr实例',
                    'provider': 'vultr'
                }
            
            if response.status_code != 200:
                return {
                    'error': f'获取实例信息失败: {response.status_code} - {response.text}',
                    'provider': 'vultr'
                }
            
            data = response.json()
            instance = data.get('instance', {})
            
            # 格式化实例信息用于确认
            instance_info = self._format_instance_for_confirmation(instance)
            
        except Exception as e:
            return {
                'error': f'获取Vultr实例信息时发生错误: {str(e)}',
                'provider': 'vultr'
            }
        
        # 检查是否提供了确认信息
        if not ip_confirmation or not name_confirmation or not operation_confirmation:
            # 转换操作名称
            operation_mapping = {
                'start': 'power_on',
                'halt': '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',
            'halt': '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': 'vultr',
                'requires_confirmation': True
            }
        
        # 执行实际操作
        try:
            operation_data = {'action': operation}
            response = requests.post(
                f'{self.base_url}/instances/{instance_id}/actions',
                headers=self.headers,
                json=operation_data,
                timeout=10
            )
            
            if response.status_code not in [200, 202, 204]:
                return {
                    'error': f'执行 {operation} 操作失败: {response.status_code} - {response.text}',
                    'provider': 'vultr'
                }
            
            return {
                'provider': 'vultr',
                'instance_id': instance_id,
                'operation_success': True,
                'operation': operation,
                'message': f'已成功提交 {operation} 操作',
                'confirmation_validated': True
            }
            
        except Exception as e:
            return {
                'error': f'执行 {operation} 操作时发生错误: {str(e)}',
                'provider': 'vultr'
            }
Behavior2/5

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

With no annotations provided, the description carries full burden. It discloses a behavioral trait ('需要三次确认' - requires three confirmations), indicating a safety or confirmation mechanism, which adds some value. However, it lacks details on permissions, side effects (e.g., downtime, data loss), rate limits, or response behavior, leaving significant gaps for a destructive operation like rebooting.

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 extremely concise with a single sentence in Chinese: '重启Vultr实例(需要三次确认)'. It's front-loaded with the core action and includes a brief constraint, with zero wasted words, making it highly efficient for an agent to parse quickly.

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, 0% schema coverage, and an output schema (which helps but isn't described), the description is incomplete. It mentions a confirmation requirement but lacks critical details like permissions, consequences, or how to use the parameters, leaving the agent under-informed for safe and effective use.

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 schema provides no parameter descriptions. The description mentions '需要三次确认' (requires three confirmations), which loosely relates to the three confirmation parameters (ip_confirmation, name_confirmation, operation_confirmation), but doesn't explain their purpose, format, or how they differ. It adds minimal meaning beyond the schema, failing to compensate for the coverage gap.

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 verb ('重启' meaning 'reboot') and resource ('Vultr实例' meaning 'Vultr instance'), making the purpose unambiguous. It doesn't explicitly differentiate from sibling tools like 'reboot_alibaba_instance' or 'reboot_digitalocean_droplet', but the provider specificity is inherent in the tool name, so it's clear but lacks explicit sibling differentiation.

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 hints at a usage constraint but doesn't explain when to use this tool versus alternatives like 'manage_instance_power' or 'power_off_vultr_instance'. No explicit guidance on prerequisites, scenarios, or exclusions is provided, leaving the agent with minimal context for selection.

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