Skip to main content
Glama
dvvincent

VergeOS MCP Server

by dvvincent

get_vm_nics

Retrieve network interface details for a specific virtual machine in VergeOS virtualization platforms to manage connectivity and monitor network configurations.

Instructions

Get network interfaces for a VM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesVM ID

Implementation Reference

  • Core handler implementation for get_vm_nics tool. Fetches the VM details to obtain machine ID, queries the VergeOS API for machine_nics, filters results, and returns the network interfaces.
    async getVMNics(vmId) {
      // Get VM to find machine ID
      const vm = await this.getVM(vmId);
      const machineId = vm.machine;
      const nics = await this.request(
        `/api/v4/machine_nics?machine=${machineId}&fields=most`
      );
      // Filter to only this machine's NICs (API quirk)
      return nics.filter((nic) => nic.machine === machineId);
    }
  • Input schema definition for the get_vm_nics tool in the TOOLS array, specifying required VM ID parameter.
      name: "get_vm_nics",
      description: "Get network interfaces for a VM",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "number",
            description: "VM ID",
          },
        },
        required: ["id"],
      },
    },
  • src/index.js:557-559 (registration)
    Dispatch/registration in the tool call handler switch statement, invoking the getVMNics method.
    case "get_vm_nics":
      result = await api.getVMNics(args.id);
      break;
  • Alternative handler implementation in direct proxy mode with additional mapping of NIC fields including MAC, IP, etc.
    async function getVMNics(vmId) {
      // Get VM to find machine ID
      const vm = await getVM(vmId);
      const machineId = vm.machine;
      const nics = await apiRequest(`/api/v4/machine_nics?machine=${machineId}&fields=all`);
      return nics.filter(n => n.machine === machineId).map(n => ({
        id: n.$key,
        name: n.name,
        mac: n.macaddress,
        network_id: n.vnet,
        ip: n.ipaddress,
        interface: n.interface,
        enabled: n.enabled,
      }));
    }
  • Schema for get_vm_nics in the direct proxy TOOLS array.
    { name: "get_vm_nics", description: "Get VM network interfaces", inputSchema: { type: "object", properties: { id: { type: "number", description: "VM ID" } }, required: ["id"] } },
    { name: "get_vm_drives", description: "Get VM disk drives", inputSchema: { type: "object", properties: { id: { type: "number", description: "VM ID" } }, required: ["id"] } },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states a read operation ('Get'), implying it is non-destructive, but does not cover aspects like error handling, rate limits, authentication needs, or what the output format might be (e.g., list of NICs with details). This leaves significant gaps for a tool with no structured safety hints.

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, direct sentence with no wasted words, making it highly concise and front-loaded. It efficiently communicates the core purpose without unnecessary elaboration, earning a top score for brevity and clarity.

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 lack of annotations and output schema, the description is incomplete. It does not explain what the tool returns (e.g., NIC details, error responses) or behavioral traits like permissions or side effects. For a read operation with no structured context, more information is needed to guide the agent 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?

The input schema has 100% description coverage, with the 'id' parameter clearly documented as 'VM ID'. The description does not add any meaning beyond this, such as format examples or constraints, but the schema provides adequate baseline information, justifying a score of 3.

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 ('network interfaces for a VM'), making the purpose immediately understandable. However, it does not differentiate from sibling tools like 'get_vm' or 'get_vm_status', which might also retrieve VM-related information, so it falls short of 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, such as 'get_vm' or 'list_vms', which might offer overlapping or related data. There is no mention of prerequisites, exclusions, or specific contexts for usage, 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