Skip to main content
Glama
rainhan99

Cloud Manage MCP Server

by rainhan99

get_system_status

Retrieve comprehensive system status overview for cloud servers, including power state, resource usage, and operational health monitoring.

Instructions

获取整个系统的状态概览

Returns:
    Dict: 系统状态信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:702-736 (handler)
    The get_system_status tool handler function. Decorated with @mcp.tool() for registration in the MCP server. Returns a dictionary with system status overview, including provider availability, IP detection status, and capabilities.
    @mcp.tool()
    def get_system_status() -> Dict:
        """
        获取整个系统的状态概览
        
        Returns:
            Dict: 系统状态信息
        """
        provider_status = {}
        available_count = 0
        
        for provider_name, provider in PROVIDERS.items():
            is_available = getattr(provider, 'available', False)
            provider_status[provider_name] = {
                'available': is_available,
                'error': getattr(provider, 'error', None) if not is_available else None
            }
            if is_available:
                available_count += 1
        
        return {
            'system_status': 'operational' if available_count > 0 else 'limited',
            'total_providers': len(PROVIDERS),
            'available_providers': available_count,
            'provider_status': provider_status,
            'ip_detection_enabled': bool(IPINFO_API_TOKEN),
            'security_features_enabled': True,
            'version': '2.0.0',
            'capabilities': {
                'aws': '只读查询',
                'digitalocean': '查询和电源管理',
                'vultr': '查询和电源管理', 
                'alibaba': '查询和电源管理'
            }
        }
  • main.py:702-702 (registration)
    Registration of the get_system_status tool via @mcp.tool() decorator on the handler function.
    @mcp.tool()
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 of behavioral disclosure. While it mentions returning a dictionary of system status information, it doesn't specify what 'entire system' means (e.g., all cloud providers, local infrastructure, or something else), whether there are authentication requirements, rate limits, or what specific data is included in the status overview.

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

Conciseness3/5

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

The description is brief with two sentences, but the second sentence 'Returns: Dict: 系统状态信息' is redundant given that an output schema exists. The first sentence is front-loaded but could be more informative about what 'system status' entails.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that the tool has 0 parameters, 100% schema coverage, and an output schema exists, the description doesn't need to explain parameters or return values. However, for a tool with no annotations and many sibling tools, it should provide more context about what 'system status' includes and how it differs from other status-related tools to be complete.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter information, and it correctly doesn't mention any parameters, maintaining a baseline score of 4 for this scenario.

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 tool's purpose as '获取整个系统的状态概览' (get an overview of the entire system's status), which is a specific verb+resource combination. However, it doesn't distinguish itself from sibling tools like 'check_provider_availability' or various monitoring tools, which might provide overlapping or related status information.

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. With many sibling tools focused on specific providers or instances, there's no indication of whether this tool provides a higher-level summary, aggregates data from other tools, or serves a different purpose entirely.

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