Skip to main content
Glama
rainhan99

Cloud Manage MCP Server

by rainhan99

get_supported_providers

Retrieve a list of available cloud service providers for managing cloud servers, enabling users to identify supported platforms for operations like power management and resource tracking.

Instructions

获取支持的云服务提供商列表

Returns:
    Dict: 支持的云服务提供商信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:627-658 (handler)
    The main handler function for the 'get_supported_providers' MCP tool. It is decorated with @mcp.tool() which registers it with the MCP server. The function iterates over the PROVIDERS dictionary, fetches provider info using get_cloud_provider_info, and constructs a detailed status report including availability and features.
    @mcp.tool()
    def get_supported_providers() -> Dict:
        """
        获取支持的云服务提供商列表
        
        Returns:
            Dict: 支持的云服务提供商信息
        """
        providers_status = {}
        
        for provider_name, provider in PROVIDERS.items():
            provider_info = get_cloud_provider_info(provider_name)
            providers_status[provider_name] = {
                'name': provider_info['name'],
                'description': provider_info['description'],
                'permissions': provider_info['permissions'],
                'supported_operations': provider_info['supported_operations'],
                'available': getattr(provider, 'available', False),
                'error': getattr(provider, 'error', None) if not getattr(provider, 'available', False) else None
            }
        
        return {
            'total_providers': len(PROVIDERS),
            'providers': providers_status,
            'ip_detection_available': bool(IPINFO_API_TOKEN),
            'security_features': [
                '三次确认机制(IP、名称、操作类型)',
                'AWS只读权限',
                '其他平台禁止删除操作',
                '智能安全检查'
            ]
        }
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 states the tool returns a dictionary of provider information, it doesn't describe what that information includes (e.g., provider names, capabilities, status), whether the data is cached or real-time, or any authentication/rate limit considerations. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 structure could be improved. The first sentence states the purpose clearly, but the second ('Returns: Dict: 支持的云服务提供商信息') is redundant with what an output schema would provide (output schema exists). This repetition slightly reduces efficiency, though overall it's not verbose.

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 the tool's simplicity (0 parameters, output schema exists), the description is somewhat complete but has gaps. The output schema handles return values, so the description doesn't need to explain those. However, for a tool with no annotations, it should provide more behavioral context (e.g., what 'supported' means, data freshness). It's adequate but could be more informative for agent usage.

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, and schema description coverage is 100% (though trivial since there are no parameters). The description doesn't need to explain any parameters, which is appropriate. It gets a baseline 4 since there are no parameters to document, and it correctly avoids unnecessary parameter explanations.

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: '获取支持的云服务提供商列表' (Get supported cloud service provider list). It uses a specific verb ('获取' - get) and resource ('云服务提供商列表' - cloud service provider list), making the function immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'check_provider_availability' or 'get_instance_by_provider', which prevents a perfect score.

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 multiple sibling tools that interact with specific providers (e.g., 'get_aws_instance_info', 'list_alibaba_instances'), there's no indication that this tool should be used to discover available providers before using provider-specific tools. The description lacks any 'when-to-use' context or prerequisites.

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