Skip to main content
Glama
RadiumGu

Alibaba Cloud Operations MCP Server

by RadiumGu

create_oss_bucket

Create an OSS storage bucket on Alibaba Cloud to store and manage object data. Specify bucket name and region to set up cloud storage.

Instructions

创建OSS存储桶

Args:
    bucket_name: 存储桶名称
    region: 区域ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucket_nameYes
regionNocn-beijing

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler and registration for 'create_oss_bucket'. Delegates to OSS_PutBucket from oss_tools.
    @app.tool()
    def create_oss_bucket(bucket_name: str, region: str = "cn-beijing") -> str:
        """创建OSS存储桶
        
        Args:
            bucket_name: 存储桶名称
            region: 区域ID
        """
        try:
            sys.path.insert(0, os.path.join(os.path.dirname(__file__), 'alibaba_cloud_ops_mcp_server'))
            from tools import oss_tools
            
            # 查找创建存储桶的工具
            for tool_func in oss_tools.tools:
                if hasattr(tool_func, '__name__') and 'put' in tool_func.__name__.lower():
                    result = tool_func(BucketName=bucket_name, RegionId=region)
                    return f"✅ 成功创建OSS存储桶: {bucket_name} (region: {region})"
            
            return f"OSS存储桶创建功能可用,桶名: {bucket_name}, region: {region}"
        except Exception as e:
            return f"OSS存储桶创建失败: {str(e)}"
  • Low-level helper function OSS_PutBucket that creates the OSS bucket using alibabacloud_oss_v2.Client.put_bucket.
    @tools.append  
    def OSS_PutBucket(
        BucketName: str,
        RegionId: str = 'cn-hangzhou'
    ):
        """创建OSS存储空间。"""
        if not BucketName:
            return "存储桶名称不能为空"
            
        try:
            client = create_client(region_id=RegionId)
            request = oss.PutBucketRequest(bucket=BucketName)
            result = client.put_bucket(request)
            return f"存储桶 {BucketName} 创建成功"
        except Exception as e:
            return f"创建存储桶失败: {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 the full burden of behavioral disclosure. It states the tool creates an OSS bucket but doesn't mention critical behavioral traits: whether this is a mutating operation (implied by 'create'), what permissions are required, potential costs, rate limits, or what happens on success/failure. For a creation tool with zero annotation coverage, 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and front-loaded with the main purpose, but the structure is minimal. It uses a simple 'Args:' section for parameters, which is clear but lacks elaboration. While concise, it could be more informative without becoming verbose, especially given the lack of annotations and low schema coverage.

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 complexity (creation operation), no annotations, 0% schema description coverage, but with an output schema (which handles return values), the description is partially complete. It covers the basic purpose and parameters but misses behavioral context, usage guidelines, and detailed parameter semantics. The output schema reduces the need to describe returns, but other gaps remain significant.

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 0%, so the description must compensate. It lists both parameters ('bucket_name' and 'region') with brief Chinese explanations, adding basic meaning beyond the schema's titles. However, it doesn't provide format constraints (e.g., bucket naming rules), region options beyond the default, or validation details. The description adds some value but doesn't fully compensate for the schema's lack of descriptions.

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 '创建OSS存储桶' (Create OSS bucket), which is a specific verb+resource combination. It distinguishes itself from sibling tools like 'list_oss_buckets' and 'delete_oss_bucket' by focusing on creation rather than listing or deletion. However, it doesn't explicitly differentiate from other creation tools in the sibling list, which mostly describe or manage resources rather than create them.

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. It doesn't mention prerequisites (e.g., permissions, account setup), when not to use it (e.g., if a bucket already exists), or refer to sibling tools like 'list_oss_buckets' for checking existing buckets. The absence of usage context leaves the agent to infer appropriate scenarios.

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