Skip to main content
Glama
aliyun

AlibabaCloud MCP Server

Official
by aliyun

StopInstances

Stop multiple AlibabaCloud ECS instances simultaneously to manage resources efficiently. Specify instance IDs and region for controlled shutdown.

Instructions

批量停止ECS实例,适用于需要同时管理和停止多台ECS实例的场景。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ForeceStopNoIs forced shutdown required
InstanceIdsYesAlibabaCloud ECS instance ID List
RegionIdNoAlibabaCloud region IDcn-hangzhou

Implementation Reference

  • Handler function OOS_StopInstances for bulk stopping ECS instances using OOS template ACS-ECS-BulkyStopInstances.
    @tools.append
    def OOS_StopInstances(
        InstanceIds: List[str] = Field(description='AlibabaCloud ECS instance ID List'),
        RegionId: str = Field(description='AlibabaCloud region ID', default='cn-hangzhou'),
        ForeceStop: bool = Field(description='Is forced shutdown required', default=False)
    ):
        """批量停止ECS实例,适用于需要同时管理和停止多台ECS实例的场景。"""
        
        parameters = {
            'regionId': RegionId,
            'resourceType': 'ALIYUN::ECS::Instance',
            'targets': {
                'ResourceIds': InstanceIds,
                'RegionId': RegionId,
                'Type': 'ResourceIds'
            },
            'forceStop': ForeceStop
        }
        return _start_execution_sync(region_id=RegionId, template_name='ACS-ECS-BulkyStopInstances', parameters=parameters)
  • Registers all OOS tools, including OOS_StopInstances, with the FastMCP server instance.
    for tool in oos_tools.tools:
        mcp.tool(tool)
  • Helper to synchronously start and poll OOS execution until completion or failure.
    def _start_execution_sync(region_id: str, template_name: str, parameters: dict):
        client = create_client(region_id=region_id)
        start_execution_request = oos_20190601_models.StartExecutionRequest(
            region_id=region_id,
            template_name=template_name,
            parameters=json.dumps(parameters)
        )
        start_execution_resp = client.start_execution(start_execution_request)
        execution_id = start_execution_resp.body.execution.execution_id
    
        while True:
            list_executions_request = oos_20190601_models.ListExecutionsRequest(
                region_id=region_id,
                execution_id=execution_id
            )
            list_executions_resp = client.list_executions(list_executions_request)
            status = list_executions_resp.body.executions[0].status
            if status == FAILED:
                status_message = list_executions_resp.body.executions[0].status_message
                raise exception.OOSExecutionFailed(reason=status_message)
            elif status in END_STATUSES:
                return list_executions_resp.body
            time.sleep(1)
  • Creates OOS client configured for the given region.
    def create_client(region_id: str) -> oos20190601Client:
        config = create_config()
        config.endpoint = f'oos.{region_id}.aliyuncs.com'
        return oos20190601Client(config)
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 mentions batch stopping but lacks critical behavioral details: whether this is destructive (likely yes, but not stated), permission requirements, rate limits, error handling, or what happens to running workloads. The description is too vague for a mutation tool with no annotation coverage.

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 a single, efficient sentence that front-loads the core purpose. It avoids unnecessary words, though it could be slightly more structured by separating purpose from usage context.

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

Completeness2/5

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

Given this is a mutation tool (stopping instances) with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., destructiveness, side effects), error cases, or return values, which are crucial for safe agent operation in a cloud environment.

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?

Schema description coverage is 100%, so the schema already documents all parameters (InstanceIds, ForceStop, RegionId). The description adds no additional parameter semantics beyond implying batch operations via '批量' (batch), which is redundant with the array type of InstanceIds. Baseline 3 is appropriate when schema does the heavy lifting.

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 action ('批量停止' - batch stop) and resource ('ECS实例' - ECS instances), making the purpose evident. It distinguishes from siblings like StopRDSInstances by specifying ECS instances, but doesn't explicitly differentiate from RebootInstances or DeleteInstances, which are also instance management tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides implied usage context ('适用于需要同时管理和停止多台ECS实例的场景' - suitable for scenarios requiring simultaneous management and stopping of multiple ECS instances), suggesting batch operations. However, it doesn't explicitly state when to use this versus alternatives like RebootInstances or DeleteInstances, nor does it mention prerequisites or exclusions.

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

Related 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/aliyun/alibaba-cloud-ops-mcp-server'

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