Skip to main content
Glama
RadiumGu

Alibaba Cloud Operations MCP Server

by RadiumGu

describe_ecs_zones

Retrieve available zones for Alibaba Cloud ECS instances to help deploy resources in optimal locations. Specify a region to get zone details for infrastructure planning.

Instructions

查询ECS可用区列表

Args:
    region: 区域ID,如cn-beijing

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNocn-beijing

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'describe_ecs_zones' tool. It is registered via the @app.tool() decorator. The function imports common_api_tools and attempts to find and invoke a tool function containing 'zone' in its name with the provided region. If not found, it returns a message indicating the feature is available. This appears to be a wrapper/placeholder implementation.
    @app.tool()
    def describe_ecs_zones(region: str = "cn-beijing") -> str:
        """查询ECS可用区列表
        
        Args:
            region: 区域ID,如cn-beijing
        """
        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 'zone' in tool_func.__name__.lower():
                    result = tool_func(RegionId=region)
                    return str(result)
            
            return f"ECS可用区查询功能可用,查询region: {region}"
        except Exception as e:
            return f"ECS可用区查询失败: {str(e)}"
  • The @app.tool() decorator registers the describe_ecs_zones function as an MCP tool.
    @app.tool()
  • Input schema defined by function signature: region (str, default 'cn-beijing'). Output: str. Includes docstring describing the parameter.
    def describe_ecs_zones(region: str = "cn-beijing") -> str:
        """查询ECS可用区列表
        
        Args:
            region: 区域ID,如cn-beijing
        """
  • Configuration file listing 'DescribeZones' as one of the ECS APIs, potentially used by dynamic tool generators to create actual API callers, though not directly used by this tool.
    'DescribeZones',
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states it's a query operation ('查询'), implying read-only behavior, but doesn't mention authentication requirements, rate limits, pagination, error conditions, or what the output contains. For a tool with no annotation coverage, this is insufficient behavioral context.

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 two sentences: one stating the purpose, one explaining the parameter. Both sentences earn their place, and the structure is clear with purpose first followed by parameter details. Minor deduction for not being perfectly front-loaded with all essential information.

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 values), 1 parameter, and no annotations, the description is minimally complete but has gaps. It covers the basic purpose and parameter, but lacks usage guidance and behavioral context that would be helpful for an AI agent. For a simple query tool with output schema, it's adequate but not comprehensive.

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?

With only 1 parameter and 0% schema description coverage, the description compensates well by providing the parameter name 'region' with a clear example ('如cn-beijing'). This adds meaningful semantic context beyond what the bare schema provides, though it doesn't explain format constraints or valid values beyond the example.

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 '查询ECS可用区列表' (Query ECS availability zone list), which is a specific verb+resource combination. It distinguishes from siblings like describe_ecs_instances or describe_ecs_regions by focusing specifically on zones. However, it doesn't explicitly differentiate from all siblings in the description text itself.

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 describe_* siblings (describe_ecs_instances, describe_ecs_regions, describe_rds_instances, etc.) but no indication of when this specific zone-listing tool is appropriate versus other describe operations.

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