Skip to main content
Glama
RadiumGu

Alibaba Cloud Operations MCP Server

by RadiumGu

describe_ecs_regions

List available ECS regions to deploy cloud resources in Alibaba Cloud environments.

Instructions

查询ECS可用区域列表

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The primary handler and registration for the MCP tool 'describe_ecs_regions'. Decorated with @app.tool() in FastMCP framework. It dynamically searches for a region-related tool in common_api_tools.tools and calls it if found; otherwise returns a message indicating the feature is available. Currently acts as a stub since no matching tool exists.
    @app.tool()
    def describe_ecs_regions() -> str:
        """查询ECS可用区域列表"""
        try:
            sys.path.insert(0, os.path.join(os.path.dirname(__file__), 'alibaba_cloud_ops_mcp_server'))
            from tools import common_api_tools
            
            for tool_func in common_api_tools.tools:
                if hasattr(tool_func, '__name__') and 'region' in tool_func.__name__.lower():
                    result = tool_func()
                    return str(result)
            
            return "ECS区域查询功能可用"
        except Exception as e:
            return f"ECS区域查询失败: {str(e)}"
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it's a query/list operation, implying read-only and non-destructive behavior, but doesn't disclose any behavioral traits like authentication needs, rate limits, pagination, or response format. For a tool with no annotations, this is a significant gap in transparency.

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 a single, efficient sentence in Chinese ('查询ECS可用区域列表'), directly stating the purpose without any fluff. It's appropriately sized and front-loaded, with every word earning its place.

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 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, it lacks details on behavioral aspects (e.g., read-only nature, potential errors) that would be helpful since no annotations are provided. It's complete enough for a simple query tool but could be more informative.

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% (empty schema). The description doesn't need to add parameter semantics beyond what's already clear—no inputs required. Baseline for 0 parameters is 4, as there's nothing to compensate for.

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 '查询ECS可用区域列表' clearly states the action (query/list) and resource (ECS regions/availability zones). It distinguishes from siblings like describe_ecs_instances (instances) and describe_ecs_zones (zones vs regions). However, it doesn't specify if this lists all regions or filtered ones, keeping it from 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?

No explicit guidance on when to use this tool versus alternatives. Siblings include describe_ecs_zones (which might be more granular) and describe_ecs_instances (for specific instances), but the description doesn't mention these or provide context for selection. Usage is implied by the name but not articulated.

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/RadiumGu/alicloud-ops-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server