Skip to main content
Glama
rainhan99

Cloud Manage MCP Server

by rainhan99

power_on_vultr_instance

Start a Vultr cloud instance with triple confirmation for security, enabling remote server activation 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:498-510 (registration)
    MCP tool registration for 'power_on_vultr_instance'. This decorator registers the function as an MCP tool.
    @mcp.tool()
    def power_on_vultr_instance(
        instance_id: str, 
        ip_confirmation: str = "", 
        name_confirmation: str = "", 
        operation_confirmation: str = ""
    ) -> Dict:
        """
        开启Vultr实例(需要三次确认)
        """
        return vultr_provider.power_on_instance(
            instance_id, ip_confirmation, name_confirmation, operation_confirmation
        )
  • Provider-level handler for powering on a Vultr instance. Delegates to the shared _execute_power_operation helper with 'start' action.
    def power_on_instance(
        self, 
        instance_id: str, 
        ip_confirmation: str = "", 
        name_confirmation: str = "", 
        operation_confirmation: str = ""
    ) -> Dict:
        """
        开启Vultr实例(需要三次确认)
        """
        return self._execute_power_operation(
            instance_id, 'start', ip_confirmation, name_confirmation, operation_confirmation
        )
  • Core helper function that handles instance retrieval, triple confirmation validation using utils.security, and executes the Vultr API call for power operations (start, halt, reboot). This is the exact implementation of the power-on logic.
    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'
            }
Behavior3/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 one important behavioral trait: '需要三次确认' (requires three confirmations), which explains why there are three confirmation parameters in the schema. However, it doesn't mention other critical behaviors like whether this is a destructive operation, what permissions are required, rate limits, or what happens if the instance is already powered on. The description adds some value but leaves significant gaps.

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 just one sentence containing 7 Chinese characters. It's front-loaded with the core action and includes the critical behavioral constraint. Every word earns its place with no wasted text.

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 this is a power management tool with 4 parameters, 0% schema coverage, no annotations, but with an output schema, the description is incomplete. While the output schema might handle return values, the description doesn't address the mutation nature of the operation, safety considerations, or parameter requirements. For a tool that changes instance state and requires multiple confirmations, more context is needed.

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?

With 0% schema description coverage for 4 parameters, the description must compensate but fails to do so. It mentions '需要三次确认' (requires three confirmations) which hints at the purpose of three parameters, but doesn't explain what 'instance_id' is, what format confirmations should take, or why three separate confirmations are needed versus one. The description adds minimal semantic value beyond what's obvious from parameter names.

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 'power on') and the resource ('Vultr实例' meaning 'Vultr instance'), providing a specific verb+resource combination. It distinguishes from sibling tools like 'power_off_vultr_instance' by specifying the opposite power action. However, it doesn't explicitly differentiate from 'manage_instance_power' which might handle multiple power states.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., instance must be powered off), when not to use it, or how it differs from similar tools like 'reboot_vultr_instance' or 'manage_instance_power'. The '需要三次确认' (requires three confirmations) is a behavioral constraint rather than usage guidance.

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