Skip to main content
Glama
ahmedselimmansor-ctrl

Alibaba Cloud MCP Server

vpc_list

List Virtual Private Clouds (VPCs) in a specified region, with optional page size control for paginated results.

Instructions

List Virtual Private Clouds (VPCs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionIdNo
pageSizeNo

Implementation Reference

  • Handler logic for vpc_list: calls DescribeVpcs API via Alibaba Cloud SDK with regionId and pageSize parameters.
    if (name === "vpc_list") {
      const parsed = z.object({
        regionId: z.string().default(config.ALIBABA_CLOUD_REGION_ID),
        pageSize: z.number().default(10)
      }).parse(args);
    
      return { content: [{ type: "text", text: JSON.stringify(await client.request('DescribeVpcs', { RegionId: parsed.regionId, PageSize: parsed.pageSize }, requestOption), null, 2) }] };
    }
  • Input schema for vpc_list: defines regionId (string) and pageSize (number) as optional parameters.
    inputSchema: {
      type: "object",
      properties: {
        regionId: { type: "string" },
        pageSize: { type: "number" }
      }
    }
  • Registration function registerVpcTools() that returns the tool definition array including vpc_list.
    export function registerVpcTools() {
      return [
        {
          name: "vpc_list",
          description: "List Virtual Private Clouds (VPCs).",
          inputSchema: {
            type: "object",
            properties: {
              regionId: { type: "string" },
              pageSize: { type: "number" }
            }
          }
        },
        {
          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"]
          }
        }
      ];
  • src/index.ts:31-42 (registration)
    Server registration: registerVpcTools() is spread into the tools array for the ListToolsRequestSchema handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          ...registerUniversalTool(),
          ...registerEcsTools(),
          ...registerVpcTools(),
          ...registerRdsTools(),
          ...registerRamTools(),
          ...registerAckTools(),
          ...registerSlbTools()
        ],
      };
  • src/index.ts:57-58 (registration)
    Routing: tools starting with 'vpc_' (including vpc_list) are dispatched to handleVpcTools.
    if (name.startsWith("vpc_")) {
      return await handleVpcTools(name, args);
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, pagination, or authentication requirements, leaving the agent uninformed beyond the basic operation.

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 extremely short (2 words of substance), which is concise but sacrifices essential information, making it less useful than a slightly longer but more complete explanation.

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?

For a simple list operation with optional filters, the description omits return format, parameter explanations, and any edge-case behavior, leaving significant gaps for effective agent use.

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?

With 0% schema description coverage and no parameter details in the description, the agent has no insight into the meaning, constraints, or usage of the two optional parameters (regionId, pageSize).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List Virtual Private Clouds (VPCs)' uses a specific verb and resource, clearly distinguishing it from sibling tools like vpc_create and other resource-listing tools such as ecs_list_instances.

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, nor does it mention prerequisites or contextual triggers.

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