Skip to main content
Glama
rainhan99

Cloud Manage MCP Server

by rainhan99

check_provider_availability

Check availability status for cloud service providers including AWS, DigitalOcean, Vultr, and Alibaba to verify operational status before deployment.

Instructions

检查特定云服务提供商的可用性

Args:
    provider_name (str): 提供商名称 ('aws', 'digitalocean', 'vultr', 'alibaba')
    
Returns:
    Dict: 提供商可用性信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
provider_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:660-700 (handler)
    The handler function for the 'check_provider_availability' tool. It is decorated with @mcp.tool() for registration and implements the logic to check a specific cloud provider's availability by inspecting environment variables and provider attributes.
    @mcp.tool()
    def check_provider_availability(provider_name: str) -> Dict:
        """
        检查特定云服务提供商的可用性
        
        Args:
            provider_name (str): 提供商名称 ('aws', 'digitalocean', 'vultr', 'alibaba')
            
        Returns:
            Dict: 提供商可用性信息
        """
        if provider_name not in PROVIDERS:
            return {
                'error': f'不支持的提供商: {provider_name}',
                'supported_providers': list(PROVIDERS.keys())
            }
        
        provider = PROVIDERS[provider_name]
        provider_info = get_cloud_provider_info(provider_name)
        
        # 检查必要的环境变量
        required_env_vars = {
            'aws': ['AWS_ACCESS_KEY_ID', 'AWS_SECRET_ACCESS_KEY'],
            'digitalocean': ['DIGITALOCEAN_TOKEN'],
            'vultr': ['VULTR_API_KEY'],
            'alibaba': ['ALIBABA_CLOUD_ACCESS_KEY_ID', 'ALIBABA_CLOUD_ACCESS_KEY_SECRET']
        }
        
        env_status = {}
        if provider_name in required_env_vars:
            for env_var in required_env_vars[provider_name]:
                env_status[env_var] = bool(os.getenv(env_var))
        
        return {
            'provider': provider_name,
            'provider_info': provider_info,
            'available': getattr(provider, 'available', False),
            'error': getattr(provider, 'error', None),
            'environment_variables': env_status,
            'all_env_vars_set': all(env_status.values()) if env_status else False
        }
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. While it mentions the tool checks availability and returns a dictionary, it doesn't describe what 'availability' means (API endpoints, service status, region availability), what authentication might be required, whether there are rate limits, or what specific information the dictionary contains beyond the generic '可用性信息' (availability information).

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 appropriately concise with a clear purpose statement followed by Args and Returns sections. The structure is front-loaded with the main purpose, though the Chinese-only content might limit accessibility for some agents. Every sentence serves a purpose with minimal waste.

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 has an output schema (which handles return value documentation) and only one parameter, the description is reasonably complete for its complexity level. However, the lack of behavioral context (what 'availability' means operationally) and usage guidance relative to sibling tools leaves clear gaps that could hinder effective tool selection.

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

Parameters3/5

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

The description adds some value beyond the input schema by listing the valid provider names ('aws', 'digitalocean', 'vultr', 'alibaba'), which isn't captured in the schema (0% description coverage). However, it doesn't explain what these providers represent or provide additional context about the parameter beyond the enum values.

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 '检查特定云服务提供商的可用性' (check specific cloud service provider availability), which is a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'get_system_status' or 'get_supported_providers' that might also provide availability or provider 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. There are multiple sibling tools that deal with provider information (get_supported_providers, get_system_status) and instance-level tools, but the description offers no context about when this specific availability check is appropriate versus other options.

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