Skip to main content
Glama
ahmedselimmansor-ctrl

Alibaba Cloud MCP Server

vpc_create

Create a Virtual Private Cloud (VPC) on Alibaba Cloud by specifying a CIDR block, region, and name for isolated network resources.

Instructions

Create a Virtual Private Cloud (VPC).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionIdNo
cidrBlockYese.g. 192.168.0.0/16
vpcNameNo

Implementation Reference

  • Registration of the vpc_create tool with its name, description, and inputSchema defining parameters: regionId, cidrBlock (required), vpcName.
    {
      name: "vpc_create",
      description: "Create a Virtual Private Cloud (VPC).",
      inputSchema: {
        type: "object",
        properties: {
          regionId: { type: "string" },
          cidrBlock: { type: "string", description: "e.g. 192.168.0.0/16" },
          vpcName: { type: "string" }
        },
        required: ["cidrBlock"]
      }
    }
  • Handler function that executes vpc_create logic: parses input with Zod, constructs CreateVpc API params, and calls the Alibaba Cloud VPC API (CreateVpc).
    if (name === "vpc_create") {
      const parsed = z.object({
        regionId: z.string().default(config.ALIBABA_CLOUD_REGION_ID),
        cidrBlock: z.string(),
        vpcName: z.string().optional()
      }).parse(args);
    
      const params: any = { RegionId: parsed.regionId, CidrBlock: parsed.cidrBlock };
      if (parsed.vpcName) params.VpcName = parsed.vpcName;
    
      return { content: [{ type: "text", text: JSON.stringify(await client.request('CreateVpc', params, requestOption), null, 2) }] };
    }
  • Input schema definition for vpc_create tool using JSON Schema format with properties: regionId, cidrBlock (required, described example), vpcName.
    inputSchema: {
      type: "object",
      properties: {
        regionId: { type: "string" },
        cidrBlock: { type: "string", description: "e.g. 192.168.0.0/16" },
        vpcName: { type: "string" }
      },
      required: ["cidrBlock"]
    }
  • src/index.ts:31-43 (registration)
    Top-level server registration: registerVpcTools() is called in ListToolsRequestSchema handler to provide the vpc_create tool definition.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          ...registerUniversalTool(),
          ...registerEcsTools(),
          ...registerVpcTools(),
          ...registerRdsTools(),
          ...registerRamTools(),
          ...registerAckTools(),
          ...registerSlbTools()
        ],
      };
    });
  • Helper utility createRpcClient is available but not directly used in vpc/index.ts - instead the VPC handler creates its own Core.default client directly.
    export function createRpcClient(endpoint: string, apiVersion: string) {
      // @ts-ignore
      return new Core.default({
        accessKeyId: config.ALIBABA_CLOUD_ACCESS_KEY_ID,
        accessKeySecret: config.ALIBABA_CLOUD_ACCESS_KEY_SECRET,
        endpoint,
        apiVersion,
      });
    }
Behavior1/5

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

With no annotations, the description must convey behavioral traits but only states the action 'create'. Missing critical details: idempotency, permissions required, potential overwrites, or error conditions (e.g., duplicate VPC names).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is extremely short (5 words), but this underspecifies the tool. Conciseness should not sacrifice essential context; here it provides only the bare action.

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

Completeness1/5

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

Given 3 parameters, no output schema, and no annotations, the description is grossly inadequate. It fails to explain parameter usage, return behavior, or any side effects, leaving the agent with minimal actionable guidance.

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

Parameters1/5

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

Input schema coverage is just 33% (only cidrBlock has an example description). The tool description adds no parameter information, leaving regionId and vpcName completely unexplained.

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 'Create a Virtual Private Cloud (VPC)' uses a specific verb and resource, and distinguishes from sibling tools which are primarily list/describe operations (e.g., vpc_list) or other actions like ecs_start_instance.

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 guidance is provided on when to use this tool versus alternatives, prerequisites, or scenario-specific instructions. The description is purely functional.

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/ahmedselimmansor-ctrl/Alibaba_cloud_MCP_server'

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