Skip to main content
Glama
dvvincent

VergeOS MCP Server

by dvvincent

list_vms

Retrieve and filter virtual machines in VergeOS by running status or name to manage virtualization resources.

Instructions

List all virtual machines in VergeOS. Can filter by running status or name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
runningNoFilter to only running VMs
nameNoFilter by VM name (partial match)

Implementation Reference

  • Core handler function for list_vms tool. Queries VergeOS API /vms endpoint with optional running and name filters, excludes snapshots.
    async listVMs(filters = {}) {
      let query = "?fields=most";
      if (filters.running) {
        query += "&is_running=true";
      }
      if (filters.name) {
        query += `&name=${encodeURIComponent(filters.name)}`;
      }
      // Filter out snapshots/templates by default
      const vms = await this.request(`/api/v4/vms${query}`);
      return vms.filter((vm) => !vm.is_snapshot);
    }
  • src/index.js:247-264 (registration)
    Tool registration in TOOLS array, including name, description, and input schema for list_vms.
    {
      name: "list_vms",
      description:
        "List all virtual machines in VergeOS. Can filter by running status or name.",
      inputSchema: {
        type: "object",
        properties: {
          running: {
            type: "boolean",
            description: "Filter to only running VMs",
          },
          name: {
            type: "string",
            description: "Filter by VM name (partial match)",
          },
        },
      },
    },
  • src/index.js:539-541 (registration)
    Dispatch/registration in the MCP tool call switch statement that routes 'list_vms' calls to the api.listVMs handler.
    case "list_vms":
      result = await api.listVMs(args || {});
      break;
  • Input schema definition for the list_vms tool, specifying optional running (boolean) and name (string) parameters.
    inputSchema: {
      type: "object",
      properties: {
        running: {
          type: "boolean",
          description: "Filter to only running VMs",
        },
        name: {
          type: "string",
          description: "Filter by VM name (partial match)",
        },
      },
    },
  • Usage of listVMs in resource read handler for 'vergeos://vms/list' resource.
    case "vergeos://vms/list":
      result = await api.listVMs();
      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 but only states it's a listing operation with filtering. It doesn't disclose important behavioral aspects like pagination behavior, rate limits, authentication requirements, error conditions, or what 'partial match' means for the name filter. For a tool with zero annotation coverage, this is inadequate.

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 perfectly concise - two sentences that directly state the purpose and key capability. Every word earns its place with zero wasted text. It's front-loaded with the core purpose followed by the filtering capability.

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 listing operation that likely returns structured data, the description is incomplete. It doesn't explain what information is returned about each VM, whether results are paginated, or any error handling. For a tool in a system with many sibling tools, more contextual guidance would be helpful.

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%, so the schema already fully documents both parameters. The description mentions filtering capabilities but doesn't add meaningful semantic context beyond what's in the schema descriptions. The baseline 3 is appropriate when the schema does all the parameter documentation work.

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 verb ('List') and resource ('virtual machines in VergeOS'), making the purpose immediately understandable. It distinguishes from some siblings like 'get_vm' (singular) but doesn't explicitly differentiate from other list tools like 'list_networks' or 'list_nodes' - hence not a perfect 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context through the mention of filtering capabilities ('Can filter by running status or name'), suggesting when this tool might be preferred over unfiltered alternatives. However, it doesn't provide explicit guidance on when to use this versus other VM-related tools like 'get_vm' or power management tools.

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