Skip to main content
Glama
phantosmax

CloudStack MCP Server

by phantosmax

associate_ip_address

Assign a new public IP address to your network or VPC using the CloudStack MCP Server. Specify the zone, network, or VPC ID to manage IP allocation efficiently.

Instructions

Acquire a new public IP address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkidNoNetwork ID
vpcidNoVPC ID
zoneidNoZone ID

Implementation Reference

  • The main handler function that executes the tool logic: calls the CloudStack client to associate an IP address and formats the response as MCP content.
    async handleAssociateIpAddress(args: any) {
      const result = await this.cloudStackClient.associateIpAddress(args);
      
      return {
        content: [
          {
            type: 'text',
            text: `Associated IP address. Job ID: ${result.associateipaddressresponse?.jobid}\nIP ID: ${result.associateipaddressresponse?.id}`
          }
        ]
      };
    }
  • Tool definition including name, description, and input schema (parameters: zoneid, networkid, vpcid).
    {
      name: 'associate_ip_address',
      description: 'Acquire a new public IP address',
      inputSchema: {
        type: 'object',
        properties: {
          zoneid: {
            type: 'string',
            description: 'Zone ID',
          },
          networkid: {
            type: 'string',
            description: 'Network ID',
          },
          vpcid: {
            type: 'string',
            description: 'VPC ID',
          },
        },
        additionalProperties: false,
      },
    },
  • src/server.ts:156-157 (registration)
    Tool registration in the MCP server: routes 'associate_ip_address' calls to the network handler.
    case 'associate_ip_address':
      return await this.networkHandlers.handleAssociateIpAddress(args);
  • CloudStack client helper method that sends the 'associateIpAddress' API request.
    async associateIpAddress(params: CloudStackParams): Promise<CloudStackResponse> {
      return this.request('associateIpAddress', params);
    }
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. 'Acquire' implies a write operation that creates or assigns an IP, but it doesn't specify permissions needed, whether it's idempotent, rate limits, or what happens on failure. This is a significant gap for a mutation 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 that front-loads the core action without any wasted words. It's appropriately sized for a tool with a straightforward purpose, making it easy to parse quickly.

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 with no annotations and no output schema, the description is incomplete. It doesn't explain what 'Acquire' entails (e.g., allocation, assignment), the return value, or error conditions. For a 3-parameter tool in a cloud infrastructure context, more detail is needed to guide effective use.

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%, with all three parameters (networkid, vpcid, zoneid) documented in the schema. The description adds no additional meaning about these parameters, such as their relationships or optionality. Baseline 3 is appropriate when the 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 ('Acquire') and resource ('new public IP address'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_public_ip_addresses' or 'enable_static_nat', which might handle IP addresses differently, so it doesn't reach the highest score.

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. With siblings like 'list_public_ip_addresses' for viewing IPs and 'enable_static_nat' for configuring them, there's no indication of prerequisites, context, or exclusions for this acquisition tool.

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