Skip to main content
Glama
dvvincent

VergeOS MCP Server

by dvvincent

list_networks

Retrieve all virtual networks configured in the VergeOS virtualization platform for network management and monitoring.

Instructions

List all virtual networks in VergeOS

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function in VergeOSAPI class that executes the API request to list networks from /api/v4/vnets
    async listNetworks() {
      return this.request("/api/v4/vnets?fields=most");
    }
  • src/index.js:565-567 (registration)
    Tool dispatch/registration in the CallToolRequestSchema handler switch statement
    case "list_networks":
      result = await api.listNetworks();
      break;
  • Tool schema and registration definition in the TOOLS array used for list_tools
      name: "list_networks",
      description: "List all virtual networks in VergeOS",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.js:365-372 (registration)
    Full tool object registration in TOOLS array
    {
      name: "list_networks",
      description: "List all virtual networks in VergeOS",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Also used in resource handler for vergeos://networks/list
    async listNetworks() {
      return this.request("/api/v4/vnets?fields=most");
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it lists networks but doesn't mention any behavioral traits like pagination, sorting, filtering options, rate limits, authentication requirements, or what the output format looks like. This leaves significant gaps for an agent to understand how to use it effectively.

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 that directly states the tool's purpose without any unnecessary words. It's front-loaded with the core action and resource, making it 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 simplicity (0 parameters) but lack of annotations and output schema, the description is incomplete. It doesn't address behavioral aspects like output format, pagination, or error handling, which are important for a list operation even without parameters. The description alone is insufficient for full contextual understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. A baseline of 4 is applied since no parameters exist.

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 ('List') and resource ('all virtual networks in VergeOS'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like 'get_network' (singular) or 'network_action', but the plural 'all' implies a comprehensive listing rather than retrieving a specific network.

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_network' (for a specific network) or 'network_action' (for operations on networks). The description implies it's for listing all networks, but doesn't clarify use cases, prerequisites, 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