Skip to main content
Glama
dvvincent

VergeOS MCP Server

by dvvincent

get_vm_status

Check the current operational state of a virtual machine, such as running or stopped, to monitor its availability and manage resources.

Instructions

Get the current status of a VM (running, stopped, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesVM ID

Implementation Reference

  • Primary handler function for get_vm_status tool. Fetches VM details by ID, retrieves all machine statuses, matches by machine ID, and returns formatted status information.
    async getVMStatus(id) {
      // Get VM to find machine ID, then get status
      const vm = await this.request(`/api/v4/vms/${id}?fields=most`);
      const statuses = await this.request("/api/v4/machine_status");
      const status = statuses.find(s => s.machine === vm.machine);
      
      if (!status) {
        return { vm_id: id, name: vm.name, power_state: "unknown", running: false };
      }
      
      return {
        vm_id: id,
        name: vm.name,
        machine: vm.machine,
        running: status.running,
        power_state: status.status,
        status_info: status.status_info || "",
        migratable: status.migratable,
      };
    }
  • Tool registration in the TOOLS array, including name, description, and input schema for MCP server.
    { name: "get_vm_status", description: "Get the current status of a VM", inputSchema: { type: "object", properties: { id: { type: "number", description: "VM ID" } }, required: ["id"] } },
  • Simplified handler in stdio MCP server that directly queries machine_status assuming id is machine ID.
    async getVMStatus(id) {
      return this.request(`/api/v4/machine_status?machine=${id}`);
    }
  • src/index.js:280-292 (registration)
    Tool registration definition in stdio MCP server.
      name: "get_vm_status",
      description: "Get the current status of a VM (running, stopped, etc.)",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "number",
            description: "VM ID",
          },
        },
        required: ["id"],
      },
    },
  • Handler in direct connection MCP server, similar to mcp-http-server, mapping VM ID to machine status.
    async function getVMStatus(id) {
      const vm = await apiRequest(`/api/v4/vms/${id}?fields=most`);
      const statuses = await apiRequest("/api/v4/machine_status");
      const status = statuses.find(s => s.machine === vm.machine) || {};
      return { id, name: vm.name, running: status.running || false, status: status.running ? "running" : "stopped" };
    }
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. It states it's a read operation ('Get'), implying non-destructive, but doesn't disclose behavioral traits like authentication needs, rate limits, error conditions, or what 'etc.' includes. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 waste. It front-loads the purpose clearly and uses parentheses to succinctly elaborate on 'status'. Every word earns its place, making it highly concise and well-structured.

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 no annotations, no output schema, and a simple input schema, the description is incomplete. It lacks details on return values (e.g., what specific statuses are possible), error handling, or operational context. For a tool that could involve critical system state, this leaves gaps in understanding its full behavior.

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 parameter 'id' documented as 'VM ID'. The description adds no additional meaning beyond this, such as format examples or constraints. With high schema coverage, the baseline is 3, as the schema does the heavy lifting without extra value from the description.

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 ('Get') and resource ('current status of a VM'), specifying what information is retrieved (running, stopped, etc.). It distinguishes from siblings like 'get_vm' (likely general VM info) or power control tools, but doesn't explicitly name alternatives. This makes it clear but not fully differentiated.

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 'get_vm' (which might include status) or 'list_vms' (which might show statuses). The description implies usage for checking VM state, but lacks explicit context, prerequisites, or exclusions, leaving the agent to infer based on tool names 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

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