Skip to main content
Glama
dvvincent

VergeOS MCP Server

by dvvincent

get_vm

Retrieve detailed information about a specific virtual machine using its ID to manage and monitor virtualization platforms.

Instructions

Get detailed information about a specific VM by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesVM ID

Implementation Reference

  • The core handler function for the 'get_vm' tool. It retrieves detailed VM information by proxying to the VergeOS API endpoint `/api/v4/vms/${id}?fields=most` using the shared request method.
    async getVM(id) {
      return this.request(`/api/v4/vms/${id}?fields=most`);
    }
  • The input schema definition for the 'get_vm' tool, specifying that a numeric 'id' parameter is required.
    {
      name: "get_vm",
      description: "Get detailed information about a specific VM by ID",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "number",
            description: "VM ID",
          },
        },
        required: ["id"],
      },
    },
  • src/index.js:542-544 (registration)
    The registration/dispatch logic in the tool call handler switch statement that routes 'get_vm' calls to the api.getVM method.
    case "get_vm":
      result = await api.getVM(args.id);
      break;
  • src/index.js:526-528 (registration)
    Registers the list_tools handler which returns the TOOLS array containing the 'get_vm' tool definition.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools: TOOLS };
    });
  • Alternative direct-mode handler for 'get_vm' that fetches VM details and enriches with status information, formatting a structured response.
    async function getVM(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: vm.$key,
        name: vm.name,
        machine: vm.machine,
        enabled: vm.enabled,
        running: status.running || false,
        status: status.running ? "running" : "stopped",
        cpu_cores: vm.cpu_cores,
        ram: vm.ram,
        os_family: vm.os_family,
        description: vm.description || "",
      };
    }
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. While 'Get detailed information' implies a read-only operation, it doesn't explicitly state whether this requires authentication, has rate limits, returns specific data formats, or handles errors. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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, well-structured sentence that efficiently communicates the core functionality without any wasted words. It's appropriately sized for a simple lookup tool and gets straight to the point.

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?

For a simple read operation with one parameter and 100% schema coverage, the description is minimally adequate. However, without annotations or an output schema, it doesn't provide enough context about what 'detailed information' includes, error handling, or authentication requirements, leaving some gaps in understanding the tool's 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?

The schema description coverage is 100%, with the single parameter 'id' clearly documented as 'VM ID' in the schema. The description adds no additional parameter semantics beyond what's already in the structured schema, so it meets the baseline expectation without adding extra value.

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 tool's purpose with a specific verb ('Get') and resource ('detailed information about a specific VM by ID'), making it easy to understand what the tool does. However, it doesn't explicitly distinguish this tool from its sibling 'get_vm_status' or 'list_vms', which would have earned a perfect 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 like 'get_vm_status' (for status-only info) or 'list_vms' (for listing multiple VMs). It simply states what the tool does without any context about appropriate usage scenarios or exclusions.

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