Skip to main content
Glama
dvvincent

VergeOS MCP Server

by dvvincent

reset_vm

Restart a virtual machine in VergeOS by specifying its ID to resolve issues or apply configuration changes.

Instructions

Reset/reboot a virtual machine

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesVM ID to reset

Implementation Reference

  • The core handler function for the 'reset_vm' tool. It invokes the generic vmAction method with the 'reset' action to perform the VM reset via the VergeOS API.
    async resetVM(id) {
      return this.vmAction(id, "reset");
    }
  • Supporting helper function that performs generic VM actions by sending a POST request to the VergeOS /api/v4/vm_actions endpoint.
    async vmAction(id, action) {
      return this.request("/api/v4/vm_actions", {
        method: "POST",
        headers: { "Content-Type": "application/json" },
        body: JSON.stringify({ vm: id, action }),
      });
    }
  • Tool schema definition including name, description, and input schema requiring a numeric VM 'id'.
    {
      name: "reset_vm",
      description: "Reset/reboot a virtual machine",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "number",
            description: "VM ID to reset",
          },
        },
        required: ["id"],
      },
    },
  • src/index.js:554-556 (registration)
    Registration and dispatch logic in the MCP tool call handler switch statement, routing 'reset_vm' calls to the resetVM handler.
    case "reset_vm":
      result = await api.resetVM(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 the full burden of behavioral disclosure. It implies a mutation action ('reset/reboot') but fails to specify critical details like whether this requires admin permissions, if it's destructive to data or processes, expected downtime, or error conditions. 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 extremely concise with a single, front-loaded phrase that directly states the tool's purpose. There is no wasted language or redundancy, making it efficient and 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 tool's complexity as a mutation operation with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits, usage context, and expected outcomes, which are critical for safe and effective tool invocation. The description does not compensate for the absence of structured metadata.

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?

The input schema has 100% description coverage, with the 'id' parameter clearly documented as 'VM ID to reset'. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate since the schema handles 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 ('reset/reboot') and resource ('a virtual machine'), making the purpose immediately understandable. It distinguishes itself from siblings like 'power_off_vm' and 'power_on_vm' by specifying a reboot rather than power cycling. However, it could be more specific about what 'reset' entails compared to 'reboot'.

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 like 'power_off_vm' or 'power_on_vm', nor does it mention prerequisites such as VM state requirements. It lacks context about appropriate scenarios, such as after configuration changes or during troubleshooting, leaving usage ambiguous.

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