Skip to main content
Glama
dvvincent

VergeOS MCP Server

by dvvincent

power_on_vm

Start a virtual machine on the VergeOS virtualization platform by providing its VM ID to activate resources and services.

Instructions

Power on a virtual machine

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesVM ID to power on

Implementation Reference

  • The core handler function in VergeOSAPI that powers on a VM by calling the generic vmAction API endpoint.
    async powerOnVM(id) {
      return this.vmAction(id, "poweron");
    }
  • Helper method in VergeOSAPI that performs generic VM actions via POST to /api/v4/vm_actions.
    async vmAction(id, action) {
      return this.request("/api/v4/vm_actions", {
        method: "POST",
        headers: { "Content-Type": "application/json" },
        body: JSON.stringify({ vm: id, action }),
      });
    }
  • Input schema definition for the power_on_vm tool, requiring a numeric VM ID.
      name: "power_on_vm",
      description: "Power on a virtual machine",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "number",
            description: "VM ID to power on",
          },
        },
        required: ["id"],
      },
    },
  • src/index.js:548-550 (registration)
    Tool registration in the MCP CallToolRequestHandler switch statement, dispatching to the powerOnVM handler.
    case "power_on_vm":
      result = await api.powerOnVM(args.id);
      break;
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action but doesn't cover critical aspects like required permissions, whether this is a destructive operation, potential side effects (e.g., network activation), rate limits, or what happens on failure. This leaves significant gaps for a mutation tool.

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 wasted words. It's front-loaded with the core action and resource, making it immediately clear and easy to parse.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral traits, error conditions, or result expectations, leaving the agent with insufficient context to use the tool safely and 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 the single parameter 'id' documented as 'VM ID to power on'. The description doesn't add any meaning beyond this, such as ID format or sourcing, but the schema adequately covers the parameter, meeting the baseline for high 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 ('power on') and resource ('a virtual machine'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'power_off_vm' or 'reset_vm', which would require explicit differentiation to earn a 5.

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 is provided on when to use this tool versus alternatives like 'power_off_vm' or 'reset_vm'. The description lacks context about prerequisites (e.g., VM must be powered off), exclusions, or related workflows, offering minimal usage direction.

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/dvvincent/vergeos-mcp-server'

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