Skip to main content
Glama
jkmills

Nutanix MCP Server

by jkmills

power_on_vm

Start a powered-off virtual machine using its UUID to make it operational.

Instructions

Power on a virtual machine.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vm_uuidYesThe UUID (extId) of the virtual machine

Implementation Reference

  • The async handler function that executes the power_on_vm tool. It calls the Nutanix v4 API POST endpoint at 'ahv/config/vms/{vm_uuid}/$actions/power-on' with an empty body, and returns a status indicating the power-on task was initiated along with the task's extId.
    async def handle_power_on_vm(
        client: NutanixClient, arguments: dict[str, Any]
    ) -> dict[str, Any]:
        """Power on a VM using v4 vmm API."""
        vm_uuid = arguments["vm_uuid"]
        result = await client.v4_post(
            namespace="vmm",
            path=f"ahv/config/vms/{vm_uuid}/$actions/power-on",
            body={},
        )
        return {"status": "power_on_initiated", "taskExtId": result.get("data", {}).get("extId")}
  • The tool definition / input schema for power_on_vm. It declares the tool name, description, and input schema requiring a 'vm_uuid' string parameter.
    {
        "name": "power_on_vm",
        "description": "Power on a virtual machine.",
        "inputSchema": {
            "type": "object",
            "properties": {
                "vm_uuid": {
                    "type": "string",
                    "description": "The UUID (extId) of the virtual machine",
                },
            },
            "required": ["vm_uuid"],
        },
    },
  • The VM_HANDLERS dispatch table that maps the string 'power_on_vm' to the handle_power_on_vm function. This table is imported into server.py and merged into the ALL_HANDLERS dict.
    VM_HANDLERS: dict[str, Any] = {
        "list_vms": handle_list_vms,
        "get_vm": handle_get_vm,
        "power_on_vm": handle_power_on_vm,
        "power_off_vm": handle_power_off_vm,
        "create_vm": handle_create_vm,
    }
  • Entry point that imports and calls server.main(), indirectly registering all tools including power_on_vm.
    """Allow running as python -m nutanix_mcp."""
    
    from nutanix_mcp.server import main
    
    main()
  • The ALL_HANDLERS dict in server.py merges VM_HANDLERS (which contains power_on_vm) and is used by the call_tool handler to dispatch tool requests.
    # Merge all handler dispatch tables
    ALL_HANDLERS: dict[str, Any] = {
        **VM_HANDLERS,
        **CLUSTER_HANDLERS,
        **PE_HANDLERS,
        **REPORT_HANDLERS,
        **NETWORKING_HANDLERS,
    }
Behavior2/5

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

Without annotations, the description fails to disclose important behavioral traits such as whether the operation is synchronous, idempotent, or fails if VM is already on. This lack of transparency may lead to incorrect agent decisions.

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

Conciseness4/5

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

The description is a single sentence, front-loaded with the action and resource. It is efficient but could benefit from a bit more context without being verbose.

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

Completeness3/5

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

Given the tool's simplicity (one parameter, no output schema), the description covers the basics. However, missing behavioral context like state dependencies and error conditions makes it less complete.

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% for the single parameter vm_uuid, so the description adds no additional meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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 clearly states the action 'power on' on a specific resource 'virtual machine'. It is easily distinguishable from sibling tools like power_off_vm and create_vm.

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 on when to use this tool, prerequisites (e.g., VM must be powered off), or alternatives. The description assumes agents know the context, leaving ambiguity.

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/jkmills/nutanix-mcp-server'

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