Skip to main content
Glama
phantosmax

CloudStack MCP Server

by phantosmax

enable_static_nat

Map a public IP address to a virtual machine using static NAT, ensuring direct accessibility and efficient routing between the VM and external networks. Requires IP address ID and VM ID for configuration.

Instructions

Enable static NAT for an IP to a VM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipaddressidYesPublic IP address ID
virtualmachineidYesVM ID
vmguestipNoVM guest IP (for multiple IPs)

Implementation Reference

  • The main handler function that implements the enable_static_nat tool logic. It calls the CloudStack client to enable static NAT and returns a formatted text response indicating success.
    async handleEnableStaticNat(args: any) {
      const result = await this.cloudStackClient.enableStaticNat(args);
      
      return {
        content: [
          {
            type: 'text',
            text: `Enabled static NAT for IP ${args.ipaddressid} to VM ${args.virtualmachineid}. Success: ${result.enablestaticnatresponse?.success}`
          }
        ]
      };
    }
  • The tool schema definition including name, description, and input schema validation for enable_static_nat.
    {
      name: 'enable_static_nat',
      description: 'Enable static NAT for an IP to a VM',
      inputSchema: {
        type: 'object',
        properties: {
          ipaddressid: {
            type: 'string',
            description: 'Public IP address ID',
          },
          virtualmachineid: {
            type: 'string',
            description: 'VM ID',
          },
          vmguestip: {
            type: 'string',
            description: 'VM guest IP (for multiple IPs)',
          },
        },
        required: ['ipaddressid', 'virtualmachineid'],
        additionalProperties: false,
      },
    },
  • src/server.ts:158-159 (registration)
    The registration and dispatching of the enable_static_nat tool in the MCP server's CallToolRequest handler switch statement.
    case 'enable_static_nat':
      return await this.networkHandlers.handleEnableStaticNat(args);
  • Helper method in the CloudStackClient class that wraps the API request to CloudStack's enableStaticNat endpoint.
    async enableStaticNat(params: CloudStackParams): Promise<CloudStackResponse> {
      return this.request('enableStaticNat', 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 for behavioral disclosure. It states the action ('Enable') but doesn't clarify if this is a mutating operation, what permissions are required, whether it's reversible, or any side effects like network disruption. This is a significant gap for a tool that likely modifies network configurations.

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 directly states the tool's purpose without unnecessary words. It's front-loaded with the key action and resources, 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 the complexity of a networking tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'static NAT' entails, the expected outcome, error conditions, or how it interacts with other tools. For a mutating operation in this context, more detail is needed to guide the agent effectively.

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 clear parameter descriptions in the input schema (e.g., 'Public IP address ID', 'VM ID'). The tool description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 for adequate but not enhanced coverage.

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 ('Enable static NAT') and the resources involved ('for an IP to a VM'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'associate_ip_address' or 'create_firewall_rule', which might handle similar networking functions, 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, such as 'associate_ip_address' or other networking tools in the sibling list. It lacks context about prerequisites, typical scenarios, or exclusions, leaving the agent to infer usage from the tool name alone.

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