Skip to main content
Glama
rainhan99

Cloud Manage MCP Server

by rainhan99

shutdown_digitalocean_droplet

Safely power down a DigitalOcean droplet with multiple confirmation steps to prevent accidental shutdowns of cloud servers.

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:432-444 (registration)
    MCP tool registration and thin handler for shutdown_digitalocean_droplet, delegates to digitalocean_provider.shutdown_droplet
    @mcp.tool()
    def shutdown_digitalocean_droplet(
        droplet_id: int, 
        ip_confirmation: str = "", 
        name_confirmation: str = "", 
        operation_confirmation: str = ""
    ) -> Dict:
        """
        优雅关闭DigitalOcean Droplet(需要三次确认)
        """
        return digitalocean_provider.shutdown_droplet(
            droplet_id, ip_confirmation, name_confirmation, operation_confirmation
        )
  • Provider class method that handles the shutdown_digitalocean_droplet logic by calling the generic power operation with 'shutdown' action
    def shutdown_droplet(
        self, 
        droplet_id: int, 
        ip_confirmation: str = "", 
        name_confirmation: str = "", 
        operation_confirmation: str = ""
    ) -> Dict:
        """
        优雅关闭Droplet(需要三次确认)
        """
        return self._execute_power_operation(
            droplet_id, 'shutdown', ip_confirmation, name_confirmation, operation_confirmation
        )
  • Core handler implementing the shutdown logic: triple security confirmation, API call to DigitalOcean droplet_actions.post with type='shutdown', and response handling
    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'
            }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the three-confirmation requirement, which is a crucial behavioral trait for safety. However, it doesn't mention other important aspects like whether this is a graceful shutdown versus hard power-off, what permissions are needed, whether it's reversible, or what the output contains. 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.

Conciseness4/5

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

The description is a single, efficient sentence in Chinese that conveys the core action and a key constraint. It's front-loaded with the main purpose. However, the inclusion of '优雅' (graceful/elegant) adds a slight stylistic flourish that doesn't contribute essential information, keeping it from a perfect score.

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?

This is a destructive operation (shutdown) with no annotations, 4 parameters (3 of which are confirmation-related with unclear semantics), and an output schema exists (which reduces the need to describe returns). The description mentions the three-confirmation safety measure but fails to address critical aspects like what '优雅关闭' (graceful shutdown) entails operationally, error conditions, or how it differs from sibling tools. For a potentially risky 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 schema provides no parameter documentation. The description mentions '需要三次确认' (requires three confirmations), which hints at the purpose of the three confirmation parameters (ip_confirmation, name_confirmation, operation_confirmation) but doesn't explain what they are, their format, or why they're needed. It doesn't address the droplet_id parameter at all. The description adds minimal semantic value beyond the schema.

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 '优雅关闭DigitalOcean Droplet(需要三次确认)' clearly states the action (shutdown) and resource (DigitalOcean Droplet) with a specific behavioral constraint (requires three confirmations). It distinguishes from siblings like 'power_off_digitalocean_droplet' by implying a more controlled shutdown process, though not explicitly contrasting them.

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 usage context about safety measures. However, it doesn't specify when to use this tool versus alternatives like 'power_off_digitalocean_droplet' or 'manage_instance_power', nor does it mention prerequisites or exclusions. The guidance is minimal and implicit.

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