Skip to main content
Glama
rainhan99

Cloud Manage MCP Server

by rainhan99

reboot_digitalocean_droplet

Restart a DigitalOcean droplet to resolve issues or apply changes, requiring three confirmations for safety.

Instructions

重启DigitalOcean Droplet(需要三次确认)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
droplet_idYes
ip_confirmationNo
name_confirmationNo
operation_confirmationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:446-458 (registration)
    Registration of the MCP tool 'reboot_digitalocean_droplet' via @mcp.tool() decorator. This is the entry point handler that delegates to the DigitalOcean provider.
    @mcp.tool()
    def reboot_digitalocean_droplet(
        droplet_id: int, 
        ip_confirmation: str = "", 
        name_confirmation: str = "", 
        operation_confirmation: str = ""
    ) -> Dict:
        """
        重启DigitalOcean Droplet(需要三次确认)
        """
        return digitalocean_provider.reboot_droplet(
            droplet_id, ip_confirmation, name_confirmation, operation_confirmation
        )
  • Core handler logic for power operations including reboot. Performs security triple confirmation, validates inputs, and executes the DigitalOcean API call to reboot the droplet.
    def _execute_power_operation(
        self, 
        droplet_id: int, 
        operation: str, 
        ip_confirmation: str, 
        name_confirmation: str, 
        operation_confirmation: str
    ) -> Dict:
        """
        执行电源操作的通用函数
        """
        if not self.available:
            return {
                'error': f'DigitalOcean服务不可用: {getattr(self, "error", "未知错误")}',
                'provider': 'digitalocean'
            }
        
        # 首先获取droplet信息
        try:
            droplet_response = self.client.droplets.get(droplet_id)
            droplet = droplet_response.get("droplet", {})
            
            if not droplet:
                return {
                    'error': f'未找到ID为 {droplet_id} 的Droplet',
                    'provider': 'digitalocean'
                }
            
            # 格式化droplet信息用于确认
            droplet_info = self._format_droplet_for_confirmation(droplet)
            
        except Exception as e:
            return {
                'error': f'获取Droplet信息时发生错误: {str(e)}',
                'provider': 'digitalocean'
            }
        
        # 检查是否提供了确认信息
        if not ip_confirmation or not name_confirmation or not operation_confirmation:
            # 返回确认要求
            return require_triple_confirmation(droplet_info, operation)
        
        # 验证确认信息
        security = SecurityConfirmation()
        is_valid, error_message = security.validate_power_operation(
            droplet_info, operation, ip_confirmation, name_confirmation, operation_confirmation
        )
        
        if not is_valid:
            return {
                'error': f'确认验证失败: {error_message}',
                'provider': 'digitalocean',
                'requires_confirmation': True
            }
        
        # 执行实际操作
        try:
            action_data = {"type": operation}
            response = self.client.droplet_actions.post(droplet_id=droplet_id, body=action_data)
            
            action = response.get("action", {})
            
            return {
                'provider': 'digitalocean',
                'droplet_id': droplet_id,
                'operation_success': True,
                'action': {
                    'id': action.get("id"),
                    'status': action.get("status"),
                    'type': action.get("type"),
                    'started_at': action.get("started_at"),
                    'resource_id': action.get("resource_id")
                },
                'message': f'已成功提交 {operation} 操作,操作ID: {action.get("id")}',
                'confirmation_validated': True
            }
            
        except Exception as e:
            return {
                'error': f'执行 {operation} 操作时发生错误: {str(e)}',
                'provider': 'digitalocean'
            }
  • Helper method in DigitalOceanProvider class that specifically handles reboot by calling the generic power operation executor.
    def reboot_droplet(
        self, 
        droplet_id: int, 
        ip_confirmation: str = "", 
        name_confirmation: str = "", 
        operation_confirmation: str = ""
    ) -> Dict:
        """
        重启Droplet(需要三次确认)
        """
        return self._execute_power_operation(
            droplet_id, 'reboot', ip_confirmation, name_confirmation, operation_confirmation
        )
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the three-confirmation requirement, which is useful context about safety measures, but doesn't describe what the reboot entails (e.g., temporary downtime, data persistence, permissions needed, rate limits, or response format). For a destructive operation with zero annotation coverage, this 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 short sentence in Chinese, front-loading the core action and a key constraint. There's zero wasted text, making it efficient for quick understanding, though this brevity contributes to gaps in other dimensions.

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 description coverage, and an output schema (which helps but isn't described), the description is incomplete. It lacks parameter explanations, detailed behavioral context, and usage guidelines, making it insufficient for safe and effective tool invocation.

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 documentation. The description doesn't mention any parameters at all, failing to explain the four parameters (droplet_id and three confirmation fields) or their purposes. This leaves all parameters completely undocumented, which is inadequate given the low schema coverage.

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 ('DigitalOcean Droplet'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'reboot_alibaba_instance' or 'reboot_vultr_instance' beyond mentioning the specific provider, which is somewhat implied but not explicit.

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 provides some context about prerequisites, but offers no guidance on when to use this tool versus alternatives like 'manage_instance_power', 'shutdown_digitalocean_droplet', or other reboot tools for different providers. There's no explicit when/when-not or alternative tool recommendations.

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