Skip to main content
Glama
phantosmax

CloudStack MCP Server

by phantosmax

create_network

Initiate network creation in CloudStack by defining essential parameters such as name, display text, network offering ID, zone ID, gateway, and netmask for efficient cloud resource management.

Instructions

Create a new network

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
displaytextYesNetwork display text
gatewayNoNetwork gateway
nameYesNetwork name
netmaskNoNetwork netmask
networkofferingidYesNetwork offering ID
zoneidYesZone ID

Implementation Reference

  • The main handler function that executes the create_network tool logic by calling the CloudStack client and formatting the response.
    async handleCreateNetwork(args: any) {
      const result = await this.cloudStackClient.createNetwork(args);
      
      return {
        content: [
          {
            type: 'text',
            text: `Created network. Job ID: ${result.createnetworkresponse?.jobid}\nNetwork ID: ${result.createnetworkresponse?.id}`
          }
        ]
      };
    }
  • Defines the tool name, description, and input schema for validation.
      name: 'create_network',
      description: 'Create a new network',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Network name',
          },
          displaytext: {
            type: 'string',
            description: 'Network display text',
          },
          networkofferingid: {
            type: 'string',
            description: 'Network offering ID',
          },
          zoneid: {
            type: 'string',
            description: 'Zone ID',
          },
          gateway: {
            type: 'string',
            description: 'Network gateway',
          },
          netmask: {
            type: 'string',
            description: 'Network netmask',
          },
        },
        required: ['name', 'displaytext', 'networkofferingid', 'zoneid'],
        additionalProperties: false,
      },
    },
  • src/server.ts:152-153 (registration)
    Tool registration in the main server switch statement, dispatching calls to the handler.
    case 'create_network':
      return await this.networkHandlers.handleCreateNetwork(args);
  • Supporting CloudStack API client method that performs the actual 'createNetwork' API request.
    async createNetwork(params: CloudStackParams): Promise<CloudStackResponse> {
      return this.request('createNetwork', params);
    }
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 states 'Create a new network', implying a write/mutation operation, but doesn't disclose behavioral traits like required permissions, whether it's idempotent, rate limits, or what happens on failure. This is a significant gap for a creation tool with zero 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.

Conciseness5/5

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

The description is a single, efficient sentence with zero waste. It's front-loaded and appropriately sized for a basic tool definition, though this conciseness comes at the cost of detail in other dimensions.

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 the tool's complexity (creation/mutation with 6 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects, usage context, or return values, leaving the agent under-informed for a non-trivial operation.

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 6 parameters (e.g., name, gateway, zoneid). The description adds no meaning beyond the schema—it doesn't explain parameter relationships, dependencies, or provide examples. 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.

Purpose3/5

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

The description 'Create a new network' clearly states the action (create) and resource (network), but it's vague about what kind of network (e.g., virtual, physical, cloud) and doesn't distinguish from siblings like 'list_networks' or 'create_firewall_rule'. It provides basic purpose but lacks specificity.

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

Usage Guidelines1/5

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

The description offers no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing zone or network offering IDs), exclusions, or relationships with sibling tools like 'list_networks' for reference. This leaves the agent with no usage context.

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/phantosmax/cloudstack-mcp-server'

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